Dynamic event naming

ABSTRACT

Provided are systems, methods, and computer-readable media useful for establishing custom names for calendar events. In various implementations, subjects for calendar events are established for different users such that each user&#39;s calendar includes an event subject that is customized for the user. For example, a user may not see his or her own name as an attendee or invitee in a calendar event subject but may see other attendees or invitees listed. For calendar events with many attendees or invitees, a custom event subject can indicate names of one or several attendees or invitees, which may be favorites or other higher priority contacts for a user, with all other attendees or invitees identified generically, such as indicated by the number of names not shown.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a continuation-in-part of U.S. Non-Provisionalapplication Ser. No. 16/160,865, filed on Oct. 15, 2018, which claimsthe benefit of and priority to U.S. Provisional Application No.62/713,450, filed on Aug. 1, 2018. This application is also acontinuation-in-part of PCT Application PCT/US2019/044707, which claimsthe benefit of and priority to U.S. Non-Provisional application Ser. No.16/160,865, filed on Oct. 15, 2018, and U.S. Provisional Application No.62/713,450, filed on Aug. 1, 2018. These applications are herebyincorporated by reference in their entireties.

BRIEF SUMMARY

Provided are systems, methods, including computer-implemented methods,and computer-program products for an event monitoring system. In variousexamples, the event monitoring system can enable attendees to a calendarevent, as well as other individuals, to use network-connected computingdevices to see when the computing devices of the attendees will arriveat the event location, and possibly also where the computing devices ofthe attendees are presently located. This information can facilitate theplanning and running of an event.

In an aspect, methods are described herein. Optionally, methods of thisaspect may be or correspond to computer-implemented methods. Methods ofthis aspect are optionally useful for tracking devices associated withusers determined to be participating in events, such as based uponacceptance of a calendar invite or meeting request, such as to allow theusers to track one another or determine another user's estimated time ofarriving at the event. An example method of this aspect comprisesreceiving, such as at a server computer, input corresponding to acalendar data entry, the calendar data entry adding an event to acalendar file, such as a calendar data entry that includes an eventstart time, an event geolocation, and a user identifier; at a firstpoint in time relative to the event start time, obtaining tracking datafor a device associated with the user identifier; determining, using thetracking data, an approximate geolocation of the device; determining,using the approximate geolocation, an approximate time differencebetween a current time and a time when the device will be at the eventgeolocation; updating a location status associated with the useridentifier, the location status indicating the approximate timedifference; at a second point in time relative to the event start time,disabling tracking of the device; and at a third point in time after thesecond point in time, deleting the tracking data. Optionally, thelocation status has a null value before the first point in time and isdeleted at the third point in time.

Optionally, a method of this aspect comprises or further comprises:determining an event status associated with the user identifier, theevent status indicating that a user associated with the user identifierhas accepted a request to be included in the event; and enabling, basedon the event status, obtaining of the tracking data. Optionally, amethod of this aspect comprises or further comprises determining anevent status for a second user identifier, such as a second useridentifier that is included in the calendar data entry. Optionally, theevent status indicates that a user associated with the second useridentifier has declined a request to be included in the event.Optionally, based on the event status, obtaining of tracking data forthe second user identifier is not enabled. Optionally, the event statusindicates that a user associated with the second user identifier hasdeclined a request to be included in the event. Optionally, based on theevent status, the second user identifier is not able to obtain thelocation status associated with the user identifier.

Optionally, a method of this aspect comprises or further comprisesdetermining a display level associated with the user identifier, thedisplay level indicating an amount of detail of the location status; andoutputting the location status according to the display level, such asby outputting the location status to a second device. Optionally, thesecond device is associated with a second user identifier, such as asecond user identifier that is included in the calendar data entry.Optionally, an event status associated with the second user identifierindicates that a user associated with the second user identifier hasaccepted a request to be included in the event. Optionally, outputtingof the location status is enabled based on the event status.

Another example method of this aspect comprises receiving, such as at aserver computer, input corresponding to a calendar data entry, thecalendar data entry adding an event to a calendar file, such as acalendar data entry includes an event start time, an event geolocation,a first user identifier, a second user identifier, and a third useridentifier; determining a first event status associated with the firstuser identifier, the first event status indicating that a first userassociated with the first user identifier has accepted a first requestto be included in the event; upon determining that the first request tobe included in the event has been accepted, enabling obtaining of firsttracking data for a first smart phone associated with the first useridentifier starting from a first point in time relative to the eventstart time; determining a second event status associated with the seconduser identifier, the second event status indicating that a second userassociated with the second user identifier has accepted a second requestto be included in the event; upon determining that the second request tobe included in the event has been accepted, enabling obtaining of secondtracking data for a second smart phone associated with the second useridentifier starting from the first point in time relative to the eventstart time; determining a third event status associated with the thirduser identifier, the third event status indicating that a third userassociated with the third user identifier has accepted a third requestto be included in the event; upon determining that the third request tobe included in the event has been accepted, enabling obtaining of thirdtracking data for a third smart phone associated with the first useridentifier starting from a first point in time relative to the eventstart time; at the first point in time relative to the event start time,activating obtaining of the first tracking data for the first smartphone associated with the first user identifier, activating obtaining ofthe second tracking data for the second smart phone associated with thesecond user identifier, and activating obtaining of the third trackingdata for the third smart phone associated with the third useridentifier; determining one or more of a first approximate geolocationof the first smart phone, a first approximate time difference between acurrent time and a first time when the first smart phone will be at theevent geolocation, or a first approximate distance difference betweenthe first approximate geolocation and the event geolocation; updating afirst location status associated with the first user identifier, thefirst location status indicating one or more of the first approximategeolocation, the first approximate time difference, or the firstapproximate distance difference; transmitting the first location statusto the second smart phone and the third smart phone; determining one ormore of a second approximate geolocation of the second smart phone, asecond approximate time difference between the current time and a secondtime when the second smart phone will be at the event geolocation, or asecond approximate distance difference between the second approximategeolocation and the event geolocation; updating a second location statusassociated with the second user identifier, the second location statusindicating one or more of the second approximate geolocation, the secondapproximate time difference, or the second approximate distancedifference; transmitting the second location status to the first smartphone and the third smart phone; determining one or more of a thirdapproximate geolocation of the third smart phone, a third approximatetime difference between the current time and a third time when the thirdsmart phone will be at the event geolocation, or a third approximatedistance difference between the third approximate geolocation and theevent geolocation; updating a third location status associated with thethird user identifier, the third location status indicating one or moreof the third approximate geolocation, the third approximate timedifference, or the third approximate distance difference; transmittingthe third location status to the first smart phone and the second smartphone; and at a second point in time relative to the event start time,disabling tracking of the first smart phone, the second smart phone, andthe third smart phone.

Optionally, a method of this aspect comprises or further comprisesdetermining an updated third event status associated with the third useridentifier, the updated third event status indicating that the thirduser associated with the third user identifier has declined the thirdrequest to be included in the event; upon determining that the thirdrequest to be included in the event has been declined, disablingtracking of the third smart phone associated with the third useridentifier, disabling transmitting of the first location data and thesecond location data to the third smart phone, and disablingtransmitting of the third location data to the first smart phone and thesecond smart phone.

Optionally, determining one or more of an approximate geolocation of asmart phone, an approximate time difference between the current time anda time when the smart phone will be at the event geolocation, or anapproximate distance difference between the approximate geolocation andthe event geolocation includes receiving, from the smart phone, one ormore of the approximate geolocation of the smart phone, the approximatetime difference between the current time and the time when the smartphone will be at the event geolocation, or the approximate distancedifference between the approximate geolocation and the eventgeolocation. Optionally, determining one or more of an approximategeolocation of a smart phone, an approximate time difference between thecurrent time and a time when the smart phone will be at the eventgeolocation, or an approximate distance difference between theapproximate geolocation and the event geolocation includes receiving,from the smart phone, tracking data or information derived from thetracking data and computing, using the tracking data or informationderived from the tracking data, one or more of the approximategeolocation of the smart phone, the approximate time difference betweenthe current time and the time when the smart phone will be at the eventgeolocation, or the approximate distance difference between theapproximate geolocation and the event geolocation.

Optionally, a method of this aspect comprises or further comprisesdetermining a fourth event status associated with a fourth useridentifier included in the calendar data entry, the fourth event statusindicating that a fourth user associated with the fourth user identifierhas accepted a fourth request to be included in the event; upondetermining that the fourth request to be included in the event has beenaccepted, enabling obtaining of fourth tracking data for a fourth smartphone associated with the fourth user identifier starting from the firstpoint in time relative to the event start time; at the first point intime relative to the event start time, activating obtaining of thefourth tracking data for the third smart phone associated with thefourth user identifier; determining one or more of a fourth approximategeolocation of the fourth smart phone, a fourth approximate timedifference between the current time and a fourth time when the fourthsmart phone will be at the event geolocation, and a fourth approximatedistance difference between the fourth approximate geolocation and theevent location; updating a fourth location status associated with thefourth user identifier, the fourth location status indicating one ormore of the fourth approximate geolocation, the fourth approximate timedifference, or the fourth approximate distance difference; transmittingthe fourth location status to the first smart phone, the second smartphone, and the third smart phone; transmitting the first locationstatus, the second location status, and the third location status to thefourth smart phone; and at the second point in time relative to theevent start time, further disabling tracking of the fourth smart phone.

Optionally, a method of this aspect comprises or further comprisesdetermining a first display level associated with the first useridentifier, the first display level indicating a first amount of detailof the first location status; outputting the first location statusaccording to the first display level, such as where the first locationstatus is output to the second smart phone and the third smart phone;determining a second display level associated with the second useridentifier, the second display level indicating a second amount ofdetail of the second location status; outputting the second locationstatus according to the second display level, such as where the secondlocation status is output to the first smart phone and the third smartphone; determining a third display level associated with the third useridentifier, the third display level indicating a third amount of detailof the third location status; and outputting the third location statusaccording to the third display level, such as where the third locationstatus is output to the first smart phone and the second smart phone.Optionally, if other user identifiers or smart phones are included in amethod of this aspect, they may be treated similarly.

Optionally, a method of this aspect further comprises or furthercomprises prior to the first point in time, establishing anevent-specific group chat room; upon determining that the first requestto be included in the event has been accepted, associating the firstuser identifier with the event-specific group chat room; upondetermining that the second request to be included in the event has beenaccepted, associating the second user identifier with the event-specificgroup chat room; upon determining that the third request to be includedin the event has been accepted, associating the third user identifierwith the event-specific group chat room; receiving first messaginginformation from the first smart phone; outputting the first messaginginformation to the event-specific group chat room by transmitting thefirst messaging information to the second smart phone and the thirdsmart phone; receiving second messaging information from the secondsmart phone; outputting the second messaging information to theevent-specific group chat room by transmitting the second messaginginformation to the first smart phone and the third smart phone;receiving third messaging information from the third smart phone; andoutputting the second messaging information to the event-specific groupchat room by transmitting the third messaging information to the firstsmart phone and the second smart phone.

Optionally, a method of this aspect comprises or further comprisesdeleting the tracking data. In some cases, tracking data stored bydevices such as smart phones may be deleted in response to receiving acommand to do so. For example, a method of this aspect may comprisetransmitting an instruction to deleted tracking data. Optionally,methods of this aspect may comprise, at a third point in time after thesecond point in time, deleting the first tracking data, the secondtracking data, and the third tracking data.

In another aspect, computing devices and systems are provided. Thecomputing devices and systems of this aspect are optionally useful fortracking devices associated with users determined to be participating inevents, such as to allow the users to track one another or determineanother user's estimated time of arriving at the event. An examplecomputing device or system comprises one or more processors; and anon-transitory computer-readable medium including instructions that,when executed by the one or more processors, cause the one or moreprocessors to perform operations. Optionally, the operations comprisereceiving input corresponding to a calendar data entry, the calendardata entry adding an event to a calendar file, such as a calendar dataentry that includes an event start time, an event geolocation, and auser identifier; at a first point in time relative to the event starttime, obtaining tracking data for a device associated with the useridentifier; determining, using the tracking data, an approximategeolocation of the device; determining, using the approximategeolocation, an approximate time difference between a current time and atime when the device will be at the event geolocation; updating alocation status associated with the user identifier, the location statusindicating the approximate time difference; at a second point in timerelative to the event start time, disabling tracking of the device; andat a third point in time after the second point in time, deleting thetracking data. Optionally, the location status has a null value beforethe first point in time and is deleted at the third point in time.

Optionally, the operations comprise or further comprise determining anevent status associated with the user identifier, the event statusindicating that a user associated with the user identifier has accepteda request to be included in the event; and enabling, based on the eventstatus, obtaining of the tracking data. Optionally, the operationsinclude determining an event status for a second user identifier, suchas a second user identifier that is included in the calendar data entry.Optionally, the event status indicates that a user associated with thesecond user identifier has declined a request to be included in theevent, and, based on the event status, obtaining of tracking data forthe second user identifier is not enabled. Optionally, the event statusindicates that a user associated with the second user identifier hasdeclined a request to be included in the event, and, based on the eventstatus, the second user identifier is not able to obtain or is preventedfrom obtaining the location status associated with the user identifier.

Optionally, the operations comprise or further comprise determining adisplay level associated with the user identifier, the display levelindicating an amount of detail of the location status; and outputtingthe location status according to the display level, such as where thelocation status is output to a second device. Optionally, outputting ofthe location status is enabled based on the event status.

An example computing device or system may comprise one or moreprocessors; and a non-transitory computer-readable medium includinginstructions that, when executed by the one or more processors, causethe one or more processors to perform operations, such as methodsdescribed herein. Optionally, the operations may comprise receivinginput corresponding to a calendar data entry, the calendar data entryadding an event to a calendar file, such as a calendar data entry thatincludes an event start time, an event geolocation, a first useridentifier, a second user identifier, and a third user identifier;determining a first event status associated with the first useridentifier, the first event status indicating that a first userassociated with the first user identifier has accepted a first requestto be included in the event; upon determining that the first request tobe included in the event has been accepted, enabling obtaining of firsttracking data for a first smart phone associated with the first useridentifier starting from a first point in time relative to the eventstart time; determining a second event status associated with the seconduser identifier, the second event status indicating that a second userassociated with the second user identifier has accepted a second requestto be included in the event; upon determining that the second request tobe included in the event has been accepted, enabling obtaining of secondtracking data for a second smart phone associated with the second useridentifier starting from the first point in time relative to the eventstart time; determining a third event status associated with the thirduser identifier, the third event status indicating that a third userassociated with the third user identifier has accepted a third requestto be included in the event; upon determining that the third request tobe included in the event has been accepted, enabling obtaining of thirdtracking data for a third smart phone associated with the first useridentifier starting from a first point in time relative to the eventstart time; at the first point in time relative to the event start time,activating obtaining of the first tracking data for the first smartphone associated with the first user identifier, activating obtaining ofthe second tracking data for the second smart phone associated with thesecond user identifier, and activating obtaining of the third trackingdata for the third smart phone associated with the third useridentifier; determining one or more of a first approximate geolocationof the first smart phone, a first approximate time difference between acurrent time and a first time when the first smart phone will be at theevent geolocation, or a first approximate distance difference betweenthe first approximate geolocation and the event geolocation; updating afirst location status associated with the first user identifier, thefirst location status indicating one or more of the first approximategeolocation, the first approximate time difference, or the firstapproximate distance difference; transmitting the first location statusto the second smart phone and the third smart phone; determining one ormore of a second approximate geolocation of the second smart phone, asecond approximate time difference between the current time and a secondtime when the second smart phone will be at the event geolocation, or asecond approximate distance difference between the second approximategeolocation and the event geolocation; updating a second location statusassociated with the second user identifier, the second location statusindicating one or more of the second approximate geolocation, the secondapproximate time difference, or the second approximate distancedifference; transmitting the second location status to the first smartphone and the third smart phone; determining one or more of a thirdapproximate geolocation of the third smart phone, a third approximatetime difference between the current time and a third time when the thirdsmart phone will be at the event geolocation, or a third approximatedistance difference between the third approximate geolocation and theevent geolocation; updating a third location status associated with thethird user identifier, the third location status indicating one or moreof the third approximate geolocation, the third approximate timedifference, or the third approximate distance difference; transmittingthe third location status to the first smart phone and the second smartphone; and at a second point in time relative to the event start time,disabling tracking of the first smart phone, the second smart phone, andthe third smart phone.

Optionally, the operations comprise or further comprise determining anupdated third event status associated with the third user identifier,the updated third event status indicating that the third user associatedwith the third user identifier has declined the third request to beincluded in the event; upon determining that the third request to beincluded in the event has been declined, disabling tracking of the thirdsmart phone associated with the third user identifier, disablingtransmitting of the first location data and the second location data tothe third smart phone, and disabling transmitting of the third locationdata to the first smart phone and the second smart phone.

Optionally, determining one or more of an approximate geolocation of asmart phone, an approximate time difference between the current time anda time when the smart phone will be at the event geolocation, or anapproximate distance difference between the approximate geolocation andthe event geolocation includes receiving, from the smart phone, one ormore of the approximate geolocation of the smart phone, the approximatetime difference between the current time and the time when the smartphone will be at the event geolocation, or the approximate distancedifference between the approximate geolocation and the eventgeolocation. Optionally, determining one or more of an approximategeolocation of a smart phone, an approximate time difference between thecurrent time and a time when the smart phone will be at the eventgeolocation, or an approximate distance difference between theapproximate geolocation and the event geolocation includes receiving,from the smart phone, tracking data or information derived from thetracking data and computing, using the tracking data or informationderived from the tracking data, one or more of the approximategeolocation of the smart phone, the approximate time difference betweenthe current time and the time when the smart phone will be at the eventgeolocation, or the approximate distance difference between theapproximate geolocation and the event geolocation.

Optionally, the operations comprise or further comprise determining afourth event status associated with a fourth user identifier included inthe calendar data entry, the fourth event status indicating that afourth user associated with the fourth user identifier has accepted afourth request to be included in the event; upon determining that thefourth request to be included in the event has been accepted, enablingobtaining of fourth tracking data for a fourth smart phone associatedwith the fourth user identifier starting from the first point in timerelative to the event start time; at the first point in time relative tothe event start time, activating obtaining of the fourth tracking datafor the third smart phone associated with the fourth user identifier;determining one or more of a fourth approximate geolocation of thefourth smart phone, a fourth approximate time difference between thecurrent time and a fourth time when the fourth smart phone will be atthe event geolocation, and a fourth approximate distance differencebetween the fourth approximate geolocation and the event location;updating a fourth location status associated with the fourth useridentifier, the fourth location status indicating one or more of thefourth approximate geolocation, the fourth approximate time difference,or the fourth approximate distance difference; transmitting the fourthlocation status to the first smart phone, the second smart phone, andthe third smart phone; transmitting the first location status, thesecond location status, and the third location status to the fourthsmart phone; and at the second point in time relative to the event starttime, further disabling tracking of the fourth smart phone.

Optionally, the operations comprise or further comprise determining afirst display level associated with the first user identifier, the firstdisplay level indicating a first amount of detail of the first locationstatus; outputting the first location status according to the firstdisplay level, such as where the first location status is output to thesecond smart phone and the third smart phone; determining a seconddisplay level associated with the second user identifier, the seconddisplay level indicating a second amount of detail of the secondlocation status; outputting the second location status according to thesecond display level, such as where the second location status is outputto the first smart phone and the third smart phone; determining a thirddisplay level associated with the third user identifier, the thirddisplay level indicating a third amount of detail of the third locationstatus; and outputting the third location status according to the thirddisplay level, such as where the third location status is output to thefirst smart phone and the second smart phone.

Optionally, the operations comprise or further comprise prior to thefirst point in time, establishing an event-specific group chat room;upon determining that the first request to be included in the event hasbeen accepted, associating the first user identifier with theevent-specific group chat room; upon determining that the second requestto be included in the event has been accepted, associating the seconduser identifier with the event-specific group chat room; upondetermining that the third request to be included in the event has beenaccepted, associating the third user identifier with the event-specificgroup chat room; receiving first messaging information from the firstsmart phone; outputting the first messaging information to theevent-specific group chat room by transmitting the first messaginginformation to the second smart phone and the third smart phone;receiving second messaging information from the second smart phone;outputting the second messaging information to the event-specific groupchat room by transmitting the second messaging information to the firstsmart phone and the third smart phone; receiving third messaginginformation from the third smart phone; and outputting the secondmessaging information to the event-specific group chat room bytransmitting the third messaging information to the first smart phoneand the second smart phone.

Optionally, the operations comprise or further comprise at a third pointin time after the second point in time, deleting the first trackingdata, the second tracking data, and the third tracking data.

In another aspect, methods for dynamically generating a custom calendarevent entry are provided. Methods of this aspect may be used alone or incombination with other methods, such as with methods for trackingdevices associated with users determined to be participating in eventsas described herein. An example method of this aspect comprisesdetermining, such as by or at a server computer, input corresponding toa calendar data entry, the calendar data entry including an event starttime, one or more user identifiers, and a base event subject;generating, using the calendar data entry, one or more custom calendardata entries respectively associated with the one or more useridentifiers; and transmitting the one or more custom calendar dataentries for adding an event to calendar files associated with the one ormore user identifiers. In some examples, a custom calendar data entrymay include a respective custom event subject for a respective useridentifier and the event start time, the respective custom event subjectderived from the base event subject and the one or more useridentifiers. Optionally, a custom calendar data entry may furtherinclude one or more of an event end time, an event duration, a location,a geolocation, an address, one or more user identifiers, an eventrecurrence schedule, or any combination of these.

In some cases, a method of this aspect may comprise determining an eventtype indicating that a calendar event is host centric event. A hostcentric event may correspond to an event where the host has invitedmultiple guests to the event and a custom calendar entry for an event onthe host's calendar should identify one or more of the guests as part ofa custom event subject, while the custom calendar entry for the event onthe guest's calendar should identify only the host as part of the customevent subject and not any of the other guests. When the event type is ahost centric event, generating the one or more custom calendar dataentries respectively associated with the one or more user identifiersmay include generating a host custom event subject for a host customcalendar data entry; and generating a guest custom event subject for oneor more guest custom calendar data entries. A situation where a hostcentric event may arise may correspond to a setting where an individualis inviting guests to an event where it may be helpful for the host tohave information about all, or at least a subset, of the guests in acustom calendar subject, while the guests may only need to know theinformation about the host and not any of the other guests. In thiscase, the list of attendee names (or guest list) for the host mayinclude all guests, while the list of attendee names for the guests mayinclude only the host, for example. If the event type indicates that theevent is not a host centric event, the list of attendee names (or guestlist) may include all invited users, at least in the first instance. Thelist of attendee names (or guest list) may be modified, as describedbelow.

Optionally, methods of this aspect can determine which users haveaccepted or declined an invite to participate or be included in theevent, such as by receiving a communication indicating this. Lists ofattendee names may be modified to reflect users that have accepted, orindicate users that have declined and/or users that have neitheraccepted nor declined. A method of this aspect may optionally furthercomprise determining an event status indicating that a first userassociated with a first user identifier of the one or more useridentifiers has accepted a request to be included in the event; andgenerating one or more updated custom calendar data entries respectivelyassociated with the one or more user identifiers, the one or moreupdated custom calendar data entries including the first useridentifier. In some embodiments, the one or more updated custom calendardata entries may further include an indication of acceptance by thefirst user; or the one or more updated custom calendar data entriesinclude an updated custom event subject including the first useridentifier or a name associated with the first identifier. A method ofthis aspect may optionally further comprise determining an event statusindicating that a first user associated with a first user identifier ofthe one or more user identifiers has rejected a request to be includedin the event; removing the first user identifier from a list of the oneor more user identifiers; and generating one or more updated customcalendar data entries respectively associated with the list of the oneor more user identifiers. In some embodiments, the one or more updatedcustom calendar data entries further include an indication of rejectionby the first user; or the one or more updated custom calendar dataentries include an updated custom event subject lacking the first useridentifier or a name associated with the first identifier; or the one ormore updated custom calendar data entries lack the first useridentifier.

Creating or generating custom calendar data entries may requireanalyzing which users have accepted, which have not, how many users areparticipating in the event, which user a calendar data entry is for,and/or other aspects. The users indicated as or determined to beparticipating in the event may be referred to herein as guests. A guestlist may identify the users indicated as or determined to beparticipating in the event. Users may be identified by their name (e.g.,a first name and/or a last name or initial) or by another identifier,such as an avatar, screen name, handle, or email address.

In some embodiments, generating a particular custom calendar data entryrespectively associated with a particular user identifier comprisesdetermining a number of guests for the event using the one or more useridentifiers; and determining a particular custom event subject using thenumber of guests for the event, the base event subject, and the one ormore user identifiers. For example, determining the particular customevent subject may comprise identifying a connector word for theparticular custom event subject; determining a custom event guest liststring for the particular custom calendar event subject using the numberof guests for the event and the one or more user identifiers; andgenerating the particular custom event subject using the base eventsubject, the connector word, and the custom event guest list string.Example connector words include, but are not limited to, ‘with’,‘including’, or translations thereof. In some cases, a null, blank, orempty connector word may be used. In some cases, use of a connector wordis optional, such that a connector word need not be used in allembodiments.

Subjects for a custom calendar data entry may optionally indicate howmany other guests are participating, such as besides and/or in additionto the user the calendar data entry is for. Various different calendarapplications may be able to display more information of an event subjectthan others without a user having to open or expand the details of theevent. In some cases, an abbreviated subject may be used, such as whichmay indicate only the number of guests and a base subject (e.g., “lunchwith 3 people”). In some cases, one or a few guests may be identified,such as by name, while other guests may be shown as an aggregated numberof the other guests (e.g., “lunch with Dave and four other guests”).

In some embodiments, determining the custom event guest list stringcomprises determining a number of guests for the custom event guest liststring using the number of guests, such as where the number of guestsdoes not count the particular user identifier; generating a guest listcomprising names associated with the one or more user identifiers, suchas a guest list not including a name associated with the particular useridentifier. In some embodiments, determining the custom event guest liststring comprises determining a maximum number of names to be displayedin the custom event guest list string; determining an excess guestcount, the excess guest count corresponding to a difference between thenumber of guests and the maximum number of names; and generating asuffix for the custom event guest list string using the excess guestcount; and generating the custom event guest list string using the guestlist, and the suffix.

Depending on the user and/or the user's preferences, which and how manyother guests are shown by name in a custom event subject may bedetermined according to various factors. Optionally, guests in a guestlist may be prioritized or ranked. In some embodiments, determining thecustom event guest list string further comprises sorting or prioritizingnames in the guest list. Prioritization may take on any of a variety offorms. In some embodiments, users registered with a particularcalendaring application or system may be given higher priority thanother non-registered users. In some embodiments, guests appearing in auser's address book may be given higher priority than other guests. Insome embodiments, guests that the user is participating in othercalendar events with may be given higher priority than other guests. Insome embodiments, prioritization may be determined alphabetically oraccording to some other generic sorting algorithm. In some embodiments,prioritization may be determined based on location data. For example,guests having location history closer in proximity to location historyof the user may be given priority over other guests. In someembodiments, a guest corresponding to a host for the event or a creatoror organizer of the calendar entry may be given a higher priority thanother guests.

In some cases, users or guests may have the same names, such as twopeople named Dave. Optionally, determining the custom event guest liststring further comprises modifying the guest list to eliminate duplicatenames or invalid names. To avoid it appearing that a user may beparticipating in an event with him or herself, further identifiers maybe added or used in place of a first name when duplicate names areidentified, such as a last name, an initial, an avatar, or a handle. Insome cases, a guest may not be registered with a calendaring applicationor system and so a first name may not be established for the user, whichmay correspond to an invalid name. When a guest's name is invalid orotherwise not available, it may be desirable to not list them as anexplicitly identified guest in a custom event subject, but rather toshow them as “one other person” or as one person among others, such as“three other people.” Such a user may be optionally identified by anemail address or other handle.

When more guests are included in the event than are set to display withexplicit names (maximum number of names or maximum number displaynames), such as according to a default number of names or according touser preference, the additional guests may be identified in a suffix forthe custom event name. A suffix may correspond to “three other people”as described above, though other specific text may be used. In someembodiments generating the suffix comprises identifying a suffix firstpart using the number of guests; and identifying a suffix second partusing the excess guest count. A suffix may include a suffix first part,which may identify the number of guests beyond those which areexplicitly displayed. In general, a suffix first part may correspond toa number, which may be spelled out in letters (e.g., one, two, fifteen,etc.) or may be indicated using numerals (e.g., 1, 2, 15, etc.). Asuffix may include a suffix second part, which may specify or otherwiseindicate that the additional guests that are not displayed. Examplesuffix second parts include, but are not limited to, words and phrasessuch as, other, others, other person, other people, other guest, otherguests, other participant, other participants, variations of these, andtranslations of these. In some cases, when the number of guests is onlylarger than the number of guests to be displayed by one, that additionalguest can be indicated using a generic suffix (e.g., “one other person”)or by using their name.

It will be appreciated that, in some languages and according to aparticular suffix second part or user preference, different suffixsecond parts may be used depending on whether one or more than oneadditional name is indicated (e.g., “one other person”, and “two otherpeople”), such as to provide correct grammar. It will further beappreciated that, in some languages, additional connector words may beused, depending on the custom event subject. For example, a connectorword of “and” or a translation thereof, may be used, when appropriatefor correct grammar. Example custom subjects may or may not include sucha connector word, depending on the particular settings. For example,when one or more guest names are shown, a connector word of “and” may beused to separate the last name in the series or the suffix in the eventof suffix usage. For example, a custom event subject using “and” as aconnector word may be ‘Lunch with Dave, Randi, and one other person’. Asanother example, a custom event subject not including the word “and” maybe ‘Lunch with 3 people’.

In another aspect, computer-program products are provided herein. Anexample computer-program product of this aspect may comprise, correspondto, or be tangibly embodied as a non-transitory machine-readable storagemedium, including instructions that, when executed by one or moreprocessors of a computing device, cause the one or more processors toperform operations. Optionally, the operations may correspond to any ofthe methods described herein.

In another aspect, systems, such as computing devices are describedherein. An example system of this aspect may comprise one or moreprocessors, and a non-transitory computer-readable storage medium. Thenon-transitory computer-readable storage medium may include instructionsthat, when executed by the one or more processors, cause the one or moreprocessors to perform operations. Optionally, the operations maycorrespond to any of the methods described herein.

BRIEF DESCRIPTION OF THE DRAWINGS

Illustrative examples are described below in detail with reference tothe following figures:

FIG. 1 includes a diagram that illustrates an example of the operationof an event monitoring system;

FIG. 2 is a diagram illustrating an example of an event monitoring;

FIG. 3 is a diagram illustrating an example of a process for registeringa calendar event with a monitoring service;

FIG. 4 is a diagram illustrating another example process for registeringan event with a monitoring service;

FIG. 5 is a diagram illustrating another example process for registeringa calendar event with a monitoring service;

FIG. 6 is a diagram illustrating an example process for a monitoringservice can perform when monitoring a calendar event;

FIG. 7 is a diagram of an example timeline, which illustrates oneexample of a monitoring period relative to the timeframe of an event;and

FIG. 8 includes a flowchart illustrating an example of a process formonitoring a calendar event.

FIG. 9 includes a flowchart illustrating an example of process forinitiating generation of custom calendar entries including custom eventobjects.

FIG. 10 includes a flowchart illustrating an example of a process forgenerating custom calendar entries including dynamic event subject.

FIG. 11 includes a flowchart illustrating an example of a process forgenerating a custom guest list string for use in a dynamic eventsubject.

FIG. 12 includes a flowchart illustrating an example of a process forgenerating a custom suffix for use in a dynamic event subject.

FIG. 13A, FIG. 13B, FIG. 13C, and FIG. 13D provide schematicillustrations of calendar data entries with custom event subjects for anevent involving two users.

FIG. 14A, FIG. 14B, and FIG. 14C provide schematic illustrations ofcalendar data entries with custom event subjects for an event involvingthree users.

FIG. 15A, FIG. 15B, and FIG. 15C provide schematic illustrations ofcalendar data entries with custom event subjects for an event involvingsix users.

DETAILED DESCRIPTION

Computing devices enable people to manage schedules and events usingcalendar applications. Using a computing device, such as a computer or asmart phone, a person can set up calendar events in applications such asGoogle Calendar, Apple Calendar, Outlook, or a web browser. A calendarevent can include parameters such as a date, a start time, an end time,a location, and/or a subject, topic, or name. In some examples, acalendar application can send alerts related to a calendar event. Forexample, the calendar application can generate a visual reminder (using,for example, a pop-up window) a certain time period before the event isto start, and/or can generate a noise, send a text message, send anemail, or generate another kind of notification. In some examples, acalendar application can indicate when calendar events overlap, so thatscheduling conflicting events can be avoided. In some examples, acalendar application can link a calendar event with a mappingapplication, so that a user can trigger the mapping application from thecalendar event, and thereby see the location of the event on a mapand/or obtain directions to the event. In these and other examples,calendar applications can assist people in tracking schedules andgetting to appointments.

In some cases, a calendar application can also aid in organizing peopleinvited to attend an event. For example, the calendar application canenable a user to specify other users who are invited to join an event.In some examples, once the calendar event has been generated, thecalendar application can notify the invited users, for example bysending by email, text message, or another digital communication formatinformation about the calendar event to the invited users. In someexamples, the calendar application can further keep track of users whohave accepted the invitation, who have declined the invitation, and/orwho have not responded to the invitation. In some cases, the list ofinvited users and whether these users have responded to the invitationto join the event is visible to the user who generated the event. Insome cases, the list of invited users and the users' invitation statusis also visible to the invited users, though this may not always be thecase.

It is often the case that, even with the assistance of calendarapplications, people who have indicated that they will be at an eventwill be arrive late. Alternatively, it may simply be that the attendeeswill be arriving at different times. In these and other situations, theattendees to an event may want to know when the other attendees will bearriving. For example, if the event is a dinner party at a restaurant,the first person to arrive at the restaurant may want to inform therestaurant when the other attendees will arrive. It could also happenthat attendees to an event decide to change the plan without updatingthe calendar event, resulting in some of the attendees knowing thealternated plans while others do not. For example, a group of attendeesfor a dinner party at a restaurant may have arrived and decided to gonext door instead, leaving the remaining attendees uninformed of thechange of plans.

Many people carry network-enabled computing devices, such as smartphones and tablet computers, throughout the day, and these computingdevices provide one solution for coordinating attendees to an event. Forexample, a person can call, text, send an instant message, or emailattendees to ask the attendees when they will be arriving at the eventor where the attendees currently are. But sending a text message or anemail may not be possible in certain situations. For example, whilewalking, a person can stop and send a message, but may not be able to doso while driving a car. Phone calls, text messages, and email have afurther shortcoming, in that these forms of communication require theperson being contacted to respond, which the person might not do if theperson is also driving or is otherwise unable to use a computing deviceat the given moment. Such notifications are also more intrusive to thereceiver as the receiver will receive an alert for each incomingmessage. A further problem is that the list of people who are expectedto be at an event may not be readily available.

When more than two people are attending to an event, additionalcoordination difficulties can arise. For example, a person running latemust decide who else in the group to inform about being late, or wouldneed to initiate a group message, neither of which is an ideal solution.In the case that only one other attendee is contacted, if that person isalso late, then it is likely that the status of who is late does not getpassed to others in the group that are on time. Initiating a groupmessage may require looking up who the other attendees are and/ordeciding on an application to use for the group message, and theapplication selected may be one that not all of the other attendees useor pay attention to.

Attendees to an event may also struggle with determining an appropriatetime for contacting other attendees. For example, if one person arrivesexactly on time and does not find any of the other attendees at theevent location, the person may be hesitant to immediately contact theother attendees to ascertain when they will arrive. Sending a messageone minute after arrival time can be considered rude or intrusive,particularly when the other attendees are only a few minutes behind.Often, however, the first to arrive may delay sending messages for 10-15minutes to avoid being rude, and if the other attendees are runningquite late, the first to arrive may become frustrated and impatient withthe delay.

Many mobile computing devices have location capabilities, which enablethe geographic location of the computing device to be determined. Acomputing device can include, a Global Positioning System (GPS)receiver, for example, and/or can use cellular tower tracking and/ortriangulation to determine the device's location. Location capabilitiescan provide another method by which the attendees to an event can belocated and the time of arrival of the attendees to be determined. Forexample, using the location capabilities of a computing device, thelocation of the computing device can be tracked, and the trackinginformation can be used to determine when the computing device (and theperson carrying the computing device) will reach an event location, howfar away (distance) the device/person is from the event location, and/orthe exact location of the person/device relative to the event location.

Tracking people through the computing devices used by the people may beproblematic, however. Tracking services tend to have few boundaries, andthus only vary between off (e.g., no location data is available for adevice) and on (e.g., the device is being tracked all the time).Additionally, when on, the location data provided by a tracking servicecan be fairly precise. For reasons of privacy, safety, mentaldiscomfort, or other reasons, many people object to being tracked allthe time through their devices, and may further object to provided theirexact location. In certain circumstances, however, such as in relationto a calendar event, people may be willing to allow a limited amount oftracking of their devices, and may further allow at least some degree ofinformation about their location to be available to others that areattending the event.

In various implementations, a system where location tracking of acomputing device is only enabled in relation to a calendar event canenable attendees to the event, as well as other individuals, todetermine when attendees to the event will arrive and/or the attendees'location before, during, and/or after the event. For example, an eventmonitoring system can be configured to begin tracking the computingdevices of attendees at a point in time prior to the start of the event,such as 30 minutes or an hour before the start of the event. The eventmonitoring system can further only enable tracking of computing devicesof users who have indicated an intention to attend the event, and notfor users who have declined to join the event or who did not respond tothe invitation to join. As a further example, the event monitoringsystem can show tracking information only to other attendees to theevent, and possibly also to other users, such as a user who set up theevent, but not to others. The tracking information can include a preciselocation or only an approximate distance from the event location.Alternatively the tracking information can include only an expected timeof arrival and no location information. Once the event has ended or at apoint in time shortly thereafter (or even before), the event monitoringsystem can delete all the tracking data, since the event is over andthere is no further need for the data.

In various implementations, event monitoring system can automate themonitoring of an event, and can provide simple interfaces for users. Forexample, once a calendar event has been created and the event has beenregistered with the event monitoring system, the event monitoring systemcan determine which user devices to track, when the tracking shouldstart, when the tracking should stop, and when the tracking data shouldbe deleted. To register a calendar event with the event monitoringsystem, a user can, for example, add the event monitoring system as aninvitee to the event. In this example, as an invitee, the eventmonitoring system can obtain the parameters of the event through theinvitation. As another example, the event monitoring system can providea software application that can be linked to a user's calendar. In thisexample, the user can generate an event in the event monitoring system'ssoftware application, and the event monitoring system can add the eventto the linked calendar, as well as registering the event for monitoring.Alternatively or additionally, in some examples, when a user generates acalendar event in a calendar that is linked to the event monitoringsystem's software application, the software application canautomatically register and enable monitoring of the event.

Some implementations may allow tracking data for invitees to an event tobe relayed to other invitees so that the event participants can be madeaware of one another's location during the time surrounding the event.For example, an invitee may have their location relayed to otherinvitees on a precise basis (e.g., absolute coordinates) or on a genericbasis (e.g., distance from event location). In some cases, rather than alocation, an estimated time needed for an invitee to arrive at the eventlocation may be provided, which may allow further masking of a user'sspecific location and may provide additional privacy while stillallowing for some information about arrival time to be shared with otherusers. Optionally, once an invitee has arrived at the event's location,their location status may change from an absolute or generic location orestimated time of arrival to an indicator that they have ‘arrived’ atthe event location. In cases where the invitee then later leaves theevent, their location status can change again to indicate they have‘departed’ the event location.

In some cases, users may arrive and leave an event multiple times, suchas depending on the event duration, the circumstances around the event,or the users role at the event, and location statuses can change inmultiple different ways. In some embodiments, the status of a user wholeaves an event can change from ‘arrived’ to ‘departed.’ When the userreturns to the event, their status can change back to ‘arrived.’ In oneexample, when the user is returning to the event, which may be triggeredmanually or automatically, such as by determining that a distance fromthe user's current location and the event location is decreasing or hasdecreased at least a threshold amount, their location status can bechanged back to providing an absolute location or a generic location orto indicate an estimated time of re-arrival at the event. In othercases, however, once a user arrives at the event location, their statusmay never show an estimated arrival time again, even if they havedeparted and/or are returning to the event, though their status mayagain show ‘arrived’ once they have returned to the event.

A calendar application can also be useful for providing informationabout an event, such as which invitees have indicated that they willattend or not attend or which invitees are at or not at the event as itoccurs. Such information can be relayed to users via a participant orinvitee list, which may indicate acceptance statuses or locationstatuses, for example. In some cases, this information about theinvitees can be provided as a subject, topic, title, name or other toplevel information (all generically referred to herein as a subject) in acalendar entry so that a user may see information about the inviteeswhen looking at their calendar application without having to open thecalendar event or drill into further details of the calendar event.

Some examples may be useful for illustrating this point. If Dave andRandi are planning to have lunch, Dave may create a calendar event,using a subject of “Lunch with Randi.” While this may work well forDave's purposes, Randi's calendar will also show the event with asubject of “Lunch with Randi,” such that Randi appears to be eitherhaving lunch with himself or with another person named Randi, and soRandi cannot determine, at a glance if this lunch is actually with Daveor with another person. A more appropriate calendar event for Randi'scalendar would have a subject of “Lunch with Dave.” However, calendarapplications generally do not allow for customization of calendar eventsubjects so instead all invitees to a calendared event are shown thesame subject, which can be confusing. Due to this, users may use genericsubjects, such as “Lunch” or “Lunch with Randi and Dave,” but this stilldoes not solve all issues. This problem becomes exacerbated in variousother scenarios, such as when multiple people are invited to a calendarevent, when multiple invitees have the same name, and/or when someinvitees decline the calendar event.

As a way to overcome these issues, custom calendar event subjects (alsoreferred to as dynamic calendar event subjects) can be used. A calendarapplication can, using various techniques, indicate custom calendarsubjects for different users. It will be appreciated that the customcalendar event subject can be used by or with various calendarapplications, or event monitoring systems, event monitoring services, ormonitoring applications, such as those described herein, or standalonecalendaring applications, for example.

FIG. 1 includes a diagram that illustrates an example of the operationof an event monitoring system 100. In various examples, the eventmonitoring system 100 includes a monitoring service 110 that can managecalendar events, mange lists of users associated with calendar events,track devices of users who are attending an event, and provide thetracking data through the client devices. In various examples, themonitoring service 110 can be implemented using various softwareprocesses executing on server computers, as discussed further below. Invarious examples, the monitoring service 110 can also include softwareapplications that can execute on user devices, through which users caninteract with the monitoring service 110.

The monitoring service 110 can enable tracking of computing devices, butonly for users that have given the monitoring service 110 permission tobe tracked, only for client devices that are registered to be tracked,and only in relation to a calendar event that has been registered fortracking.

A calendar, as described herein, is a digital representation of thedays, weeks, months, and years by which time is measured. In variousexamples, the data that comprises a calendar can be stored in a digitalfile. An example of a digital file format for calendars is iCalendar. Inaddition to being able to illustrate and track time, electroniccalendars can also store meetings, appointments, tasks, and otherinformation that can be associated with a date and/or a time. Herein,meetings, appointments, tasks, and any other data that can be stored ina calendar, and can be associated with a particular date and/or time,will be referred to as a calendar event.

In various examples, the calendar event provides parameters fordetermining when to enable tracking and which devices to track. Acalendar event can generated using a calendar application executing on acomputing device, through a web browser that gives access to a web-basedcalendar or calendar interface, using a software application thatincludes calendar functionality and/or is linked to a calendarapplication or a calendar file, or using another software application. Acalendar event can include, for example, parameters such as a date, astart time (e.g., an hour or hour and minute), and an event location102, which can be provided as a street address, using GPS coordinates,as a waypoint on a map, and/or with a latitude and longitude, amongother examples. In some examples, the parameters can also include an enddate and/or time. In various examples, the parameters of a calendarevent can be stored in a structured format in a calendar file.

In various examples, the parameters of a calendar event can furtherinclude a list of users who have been invited to join the event. A user,in this context, is a digital entity that is maintained by a computingsystem, and for which various types of digital identifiers may existthat associate data with the user. For example, a user can be identifiedto a computing system by a username, which can be an alphanumericstring. In this example, the username can be associated with a useraccount on the computing system and/or on a network. The user accountcan further be associated with authentication data, such as a password,a security token, bioinformatic data, or other data that can be used togive a person access to the account, or to give the account access tothe computing system. As another example, a user can be identified by anemail address, a social media handle (e.g., a type of username), agaming handle, a mobile telephone number, or another type of identifier.In some examples, one user can be associated with multiple useraccounts. In some examples, one user can be associated with multipleemail addresses, social media handles, or other identifiers. In someexamples, more than one person (e.g., a human being) can be associatedwith the same user. For example, a team of network administrators mayeach have access to the same user account.

Users can be invited to join a calendar event in various ways. Forexample, the user who generates the calendar event can specify usernames, social media handles, or email addresses for the invitees. Usersinvited to join a calendar event may be referred to herein as invitees.In various examples, a calendar application can notify the inviteesabout the event by sending the invites an email, an instant message, atext message, a post to a social media page, or through another form ofdigital communication. In some examples, the calendar application canalso add the calendar event to the calendars of the invitees. In variousexamples, the invitee users can accept or decline the invitation to jointhe event through the email or other communication that notifies theinvitees of the event, and/or through a calendar application.

In various examples, the calendar application can associate a statuswith each invitee user. For example, when the calendar event is firstgenerated, each of the invitees users can be assigned the status“invited.” When an invitee user accepts the invitation to join theevent, the user's status can be changed from “invited” to “accepted” or“attending.” Herein, users whose status is “accepted” or “attending”will be referred to as attendees. When an invitee users declines theinvitation, the user's status can be changed from “invited” to“declined” or “not attending.” Users who do not respond to theinvitation can be left in an “invited” state. In various examples, eachuser's state can be stored as a parameter of the calendar event.

In various examples, the user who generates the calendar event can beconsidered the “owner” or “administrator” of the event. In theseexamples, the owner user's status in the calendar event can default to“attending.” In some cases, only the owner of a calendar event can addor remove invitees or make other changes to the parameters of the event.In some cases, other users can make changes to the event. For example,an owner or administrator can enable any user to make changes, or enableinvitees to make changes. Alternatively or additionally, an owner oradministrator can designate other users as owners or administrators ofthe calendar event. In some cases, only an owner or administrator of acalendar event can cancel or delete the calendar event. When a calendarevent is canceled, in various examples, the calendar applicationnotifies the attendees or all invitees that the event has been canceled.

In various examples, the owner of a calendar event can register thecalendar event with the monitoring service 110 so that attendees to theevent can be tracked. As discussed further below, various techniques canbe used to register a calendar event with the monitoring service 110.For example, the monitoring service 110 can be added as an invitee tothe calendar event. As another example, a calendar file can be linked tothe monitoring service 110, so that, when an event is added to thecalendar file, the event is automatically registered for monitoring.Linking can be accomplished, for example, enabling a calendar feed fromthe calendar file to the monitoring service 110. As another example, acalendar event can be generated using the software application providedby the monitoring service 110, and by being generated in the softwareapplication, the calendar event will be registered for tracking. In thisexample, the calendar event can also be added to a linked calendar. Asanother example, the software application can link directly to a user'scalendar, which may be accessible to the user and the softwareapplication through the user's computing device (e.g., mobile phone oranother computing device). In these and other examples, the calendarapplication can provide an Application Programming Interface (API) thatenables the software application to access the calendar.

In various examples, the monitoring service 110 can verify whetherinvitees to an event are registered with the monitoring service 110.Registration indicates a basic consent to be tracked. In some examples,the monitoring service 110 can verify whether a user is registered whenthe calendar event is registered with the monitoring service 110, when auser is invited to join the calendar event, and/or when the user acceptsthe invitation to join. When a user is not registered with themonitoring service 110, the monitoring service 110 can send the user aninvitation to register with the service by email, text message, instantmessage, or another form of digital communication. In some examples, theuser's status as not registered is indicated to the owner of thecalendar event, with a suggestion that the owner send the user apersonal invitation to join the monitoring service 110.

In various examples, users who do not register with the monitoringservice 110 will not be tracked. That is, though a user has accepted aninvitation to join the calendar event, the monitoring service 110 willnot collect tracking data for the user, and will not provide the user'slocation or estimated time of arrival at the event to other attendees tothe event.

Alternatively, in some examples, the monitoring service 110 can enabletemporary tracking or one-time tracking for only the one calendar event,with registration with the monitoring service 110 not being required. Inthese examples, the monitoring service 110 can request a username thatthe monitoring service 110 can use to obtain tracking data for thenon-registered user. The monitoring service 110 can further enable onlybasic tracking for the non-registered user, such as providing, to otherattendees, only an estimated time of arrival for the non-registereduser. Information provided to the non-registered user can similarly belimited. For example, the monitoring service 110 can hide the identitiesof other attendees from the non-registered users, instead identifyingthe other attendees by a number or a generic string, for example. Asanother example, the monitoring service 110 can provide thenon-registered user with only an estimated time of arrive for otherattendees, and not provide any indication of the other attendees'location. At a designated time after the one-time event, the monitoringservice 110 can delete any information obtained from the non-registereduser, including the username the user provided.

For registered users, the monitoring service 110 can maintain a set ofdata, including a user's status with respect to a calendar event thathas been registered with the monitoring service 110 and to which theuser has been invited. The monitoring service 110 can obtain the user'sstatus (e.g., whether the user has accepted, declined, or not respondedto the invitation to join the calendar event) from parameters providedwith the calendar event. Alternatively or additionally, the monitoringservice 110 may be able to access a calendar (e.g., a calendar file thatis linked to the monitoring service 110) that is updated by a calendarapplication when invitees accept or decline the event invitation.Alternatively or additionally, the monitoring service 110 may be able toaccess a calendar feed (e.g., a data stream whose source is anothercalendar, where the data stream includes calendar data that is beingshared from the source calendar to another calendar) that periodicallyprovides new event data and/or updates to existing events. Alternativelyor additionally, invitees may be able to accept or decline an eventusing a software application provided by the monitoring service 110, inwhich case the monitoring service 110 can obtain the invitee's statusfrom the application.

In various examples, the data the monitoring service 110 maintains for aregistered user can further include a contact list of other usersregistered with the monitoring service 110 and/or a link to a contactlist maintained by another application. In some examples, a link to acontact list outside of the monitoring service 110 can be provided sothat a registered user can access the external contact list whenselecting users to invite to an event. In these examples, users selectedfrom the external contact list who are not registered with themonitoring service 110 will not be tracked, or will need to provideexplicit consent to be tracked. For example, the monitoring service 110may generate an email or other digital message that requires anaffirmative response (e.g., clicking of button or link) to indicateconsent to be tracked. In various examples, the monitoring service 110can use contact list maintained by the monitoring service 110 todetermine information available to a registered user. For example, whena one registered user adds another registered user to the first user'scontact list, a different level of tracking information (with respect toa specific event) may be made available to the first user. For example,the first user may be able to see more detailed tracking information,such as a precise location, for users in the first user's contact list,and see less information for other users, such as only an approximatedistance from the event location.

As an alternative or an addition to a contact list, the monitoringservice 110 can, for example, maintain a list of “allowed” users and“blocked” users for each registered user, where the users in the listcan be registered or un-registered users. In this example, “allowed”users can see at least some tracking information (with respect to aspecific event) for the user associated with the lists, and “blocked”users can see no tracking information. In various examples, users whoare not registered with the monitoring service 110 can also be blocked.Non-registered users can be identified, for example, by an email addressor username or handle with another service, such as a social mediaservice. By allowing blocking of unregistered users, a user need notknow whether a user to be blocked is registered with the monitoringservice 110.

In various examples, the data that the monitoring service 110 maintainsfor a registered user can further include the information that isdisplayed for the user when the user is being tracked. For example, theuser may be able to specify a name or other character string by whichthe user will be identified to other users As another example, the usermay be able to specify the level of detail that is displayed to otherusers. Levels of detail can include, for example, whether the user hasaccepted or declined to attend to event (e.g., no location or timedata), an estimated time of arrival (e.g., no location data), anapproximate distance from the event location (e.g., imprecise locationdata), and/or a precise location. In this example, the approximatedistance from the event location and the precise location can alsoinclude an estimated time of arrival. In various examples, a registereduser can set a level of detail that applies to all events (e.g., adefault level of detail). In some examples, the user can set a level ofdetail for a specific event, for example when the user accepts aninvitation to attend the event. In some examples, the owner of the eventcan control the level of detail for all attendees. In these examples,the owner may not be able to specify a greater level of detail than anattendee has specified.

In various examples, the monitoring service 110 can also maintain, foreach registered user, a registered device. Registering a device with themonitoring service 110 indicates to the monitoring service 110 that thedevice that is registered is the device to be tracked when the user isbeing tracked. In some examples, a user can register more than onedevice. In these examples, the user may need to specify, for eachcalendar event, which device is to be used to obtain trackinginformation. Alternatively or additionally, the user may be able todesignate a “primary” device and additional devices, and the monitoringservice 110 will track the primary device unless the user indicatesotherwise.

Devices that can be registered for tracking can include variousnetwork-enabled computing devices. Examples of network-enabled computingdevices include smart phones, tablet computers, personal digitalassistants, laptop computers, and other devices that include anintegrated circuit for executing computer code, memory, and a networkinterface. Computing devices can further include devices such as desktopcomputers and server computers when these computing devices are capableof being mobile. The network interface of a network-enabled computingdevice can include an antenna for communicating with Wi-Fi networksand/or cellular networks. In some examples, a computing device canfurther include location capability, that is, the ability to determineor indicate the device's geographic location. For example, the computingdevice can include a GPS receiver and/or software for determining thedevice's location using nearby cell towers.

In various examples, when the start time of a registered calendar eventis approaching, the monitoring service 110 can determine which users totrack, or, more specifically, which devices to track. As noted above, invarious examples, only users registered with the monitoring service 110,or who have given temporary permission to be tracked, will be tracked.Additionally, in some examples, only users who have indicated anintention to attend the event will be tracked. In some cases, aregistered user may have indicated an intention to attend the event, butmay have requested that the monitoring service 110 not track the userfor this event, in which case the user will not be tracked.

In various examples, the monitoring service 110 can further determinewhen to start and stop tracking. Tracking can start, for example, anhour before the start of the event, 30 minutes before, or some othernumber of minutes before the start of the event. In some examples, theowner of the event can designate when tracking should start, or else themonitoring service 110 can determine the time. In some examples, themonitoring service 110 can stop tracking when the event starts or somenumber of minutes after the event starts (e.g., 30 minutes or a timedesignated by the owner of the event). Alternatively or additionally,tracking can stop when all attendees have arrived at the event location.Alternatively or additionally, tracking can continue until the end ofthe event, which can enable attendees to find each other at or duringthe event. In some examples, the monitoring service 110 can beconfigured to start tracking at the start of the event instead of beforethe event, and stop tracking at certain number of minutes after thestart of the event, at the end of the event, or a certain number ofminutes after the end of the event.

In some examples, an attendee user can designate when the user can betracked. For example, monitoring service's default configuration may beto start tracking 30 minutes before the event, and the attendee user canindicate that the user will only be tracked for 10 minutes before theevent. In this example, all other attendee users will be trackedstarting 30 minutes before the event.

Once tracking starts, attendee users may be able to see each other'stracking data using, for example, a software application provided by themonitoring service 110 that can execute on the users' devices. Invarious examples, the monitoring service 110 can determine the trackingdata that each user is able to see. For example, the defaultconfiguration for the monitoring service 110 can be to show all attendeeusers only an estimated time of arrival for other attendee users.Alternatively or additionally, the monitoring service 110 can beconfigured to show an approximate distance of each attendee user fromthe event location 102. Alternatively or additionally, the monitoringservice 110 can be configured to show each attendee user's approximategeographic location, for example on a map. In some examples, themonitoring service 110 can additionally show each user's probable routeto the event location 102. In some examples, the monitoring service canshow a complete or limited history of tracking during an event so thatusers can determine whether other attendees are moving in the directionof the event location.

In various examples, individual attendee users may show different levelsdetail in the users' tracking data. For example, one user may enableprecise location tracking, so that the user's geolocation is availableto other attendee users. As another example, another user may enabledisplay of only the user's distance to the event, without a preciselocation. As another example, another user may enable only the mostlimited tracking data, such as an estimated time of arrival, so that theuser's geolocation is not provided. In some examples, the owner of theevent can specify the degree of tracking data that is available, andattendee users can choose to override this setting with a setting thatis specific to each user.

In various examples, when the owner of the calendar event is not anattendee to the event, the owner may still be able to see the attendeeusers' tracking data. In some examples, the event owner may be able tosee a precise geolocation for each user, even though this level ofdetail is not available for viewing by the attendee users.

In some examples, the owner of the calendar event can designatenon-attendee users who can see the attendee users' tracking data. Thisfeature can be used, for example, when the attendees to an event arechildren and the children's parents, who are not attending the event,want to make sure the children get to the event location 102.

As noted above, the monitoring service 110 determines the tracking datafor each attendee user using tracking information that is available froma computing device that is being carried by a person registered as theuser. In some examples, the monitoring service 110 can obtain trackingdata from users' devices. For example, a computing device may have a GPSreceiver and/or may be able to determine a geolocation from nearby Wi-Fisignals or cellular antennas. In various examples, when a user registersa device with the monitoring service 110, registration includes givingthe monitoring service 110 access to the geolocation data the device isable to determine about itself. Using the geolocation data, themonitoring service 110 can determine where a device is during thetracking period, and from the device's location determine tracking datafor the device. The monitoring service 110 can then provide the trackingdata, at various levels of detail, to those monitoring the arrival ofattendees at an event.

Determining accurate and useful tracking data can require moreinformation than knowing where a device is at a given moment. Asillustrated in the example of FIG. 1, different attendees may be gettingto an event location 102 in different ways. For example, a first device114 may be being carried by a person who is walking to the eventlocation 102, while a second device 116 is in a car that is being drivento the event location 102. As a further example, a third device 118 maybe being carried by a person who is bicycling to the event location 102.In some cases, an attendee's route to the event location 102 may involvemultiple legs, which can further complicate determining the attendee'sarrival time. For example, in the example of FIG. 1, a fourth device 120may be being carried be being carried by a person who is on a train, andonce the train reaches a train station 122, the person may walk the restof the way to reach the event location 102.

Because of variations in the ways that attendees may be getting to theevent location 102, the monitoring service 110 may need to dynamicallycalculate a device's expected time of arrival at the event location 102,and may further need to modify or update the device's arrival time asthe monitoring service 110 acquires more tracking data. For example,when tracking is first enabled for an event, the monitoring service 110can monitor a device being tracked for a period of time, to determinethe device's location and the device's rate of travel. From thisinformation, the monitoring service 110 may be able to determineinformation such as whether the person carrying the device is likelywalking, in a car, riding a bicycle, on a train, or using another formof transit. The device's location, either at a given instance or overtime, can indicate, for example, that the device might be on a train oron a road, and/or the device's rate of travel can indicate a probablemode of travel (e.g., walking, running, bicycling, driving, etc.).

In various examples, once the monitoring service 110 has established adevice's mode of travel, the monitoring service 110 can make an initialcomputation for when the device is expected to reach the event location102. For example, the device's expected time of arrival can be computedfrom the device's instantaneous distance from the event location 102 andthe device's rate of travel. In some examples, the monitoring service110 may enable tracking before providing tracking data for viewing(e.g., 15 minutes, 30 minutes, or another interval of time before thetracking data is available), so that the initial expected time ofarrival more accurately reflects each attendee's expected time ofarrival. Herein, the time a device is tracked that precedes the timewhen tracking data can be viewed will be referred to as the initialtracking period and the time when tracking data is viewable will bereferred to as the primary tracking period.

In various examples, the monitoring service 110 can attempt to provide amore accurate time of arrival for a device. For example, havingestablished a probable mode of travel, the monitoring service 110 candetermine a probable route for a device, using mapping data, forexample. In this example, the device's estimated time of arrival at theevent location 102 can be computed from the distance to be traveled andthe rate of travel, among other factors. Route data can also aid themonitoring service 110 in determining that the rate of travel of adevice may change, such as in the example of the fourth device 120 thatis on a train. In some examples, the monitoring service 110 can furtheruse information such as traffic data, train schedules, current police orother emergency data, and/or weather data to determine whether theperson carrying a particular device may be slowed down for any reason,or may have to use a different route.

In various examples, the various devices that are traveling to the eventlocation 102 may be able to view the estimated time of arrival (andpossibly the location) of each of the devices of the attendees. Invarious examples, other devices can also view tracking data for thedevices traveling to the event location 102. For example, a stationarydevice 112, which, in the illustrated example, is at the event location102, may also be able to see the tracking data. The stationary device112 may be registered to the owner of the event, a person designated asbeing able to see tracking data for the event, and/or an attendee to theevent.

In various examples, a user of the stationary device 112 (and otherdevices) may be able to see the tracking data using a softwareapplication executing on the device, which is able to obtain data fromthe monitoring service 110. The software application may show, forexample, a list of names or other identifiers for each of the attendeeusers, and an expected time of arrival for each attendee. For example,the application may show text such as “arriving in 10 minutes” or“arriving at 3:05 pm.” As another example, when a device's location isavailable, the software application may show a map with the device'slocation marked. In this example, the device's probable route to theevent location 102 may also be marked. When a precise geolocation is notenabled, the application may instead show, for example, a circle aroundthe event location 102 that indicates an attendee's approximate distancefrom the event location 102.

In various examples, a device's rate of travel to the event location 102may change over the time period that the device is tracked. For example,the person carrying the first device 114 may step into a cab, or theperson carrying the second device 116 may park and walk the remainder ofthe distance. As another example, the train may be delayed, so that theperson carrying the fourth device 120 becomes stationary for a period oftime or arrives at the train station 122 later than indicated by a trainschedule. As another example, an attendee may choose to use a differentroute from the route determined by the monitoring service 110, and/ormay make a stop along the way. For these and other reasons, themonitoring service 110 can periodically update the tracking data foreach of the attendee users. For example, the monitoring service 110 canreacquire a device's location every 30 seconds, 60 seconds, 5 minutes,or over another interval of time, and can recompute a device's expectedtime of arrival. In some examples, the updated tracking data is pushedto devices, such as the stationary device 112, so that the user of thedevice is notified that the updated information is available.Alternatively, if the user is actively viewing the data on thestationary device 112, the user can then be provided with updatedinformation as soon as the data is available. In some examples, theupdated tracking data is only pulled from the monitoring service 110when a user opens the software application on a device.

As noted above, it is assumed that a person attending an event will becarrying a computing device that the person has registered with themonitoring service 110 for tracking. In some cases, however, the personmay have left the device at home or at another location, in which casethe person cannot be tracked. In these cases, the monitoring service 110may be able to determine tracking data is not available for the person,and can so indicate to other attendees. The monitoring service 110 maybe able to determine that the device is not being carried by the person,for example, by determining that the device has been stationary for acertain amount of time during the initial tracking period and/or theprimary tracking period. Alternatively or additionally, in someexamples, the monitoring service 110 may allow users to set a “home”location, a “work” location, or other locations, which the monitoringservice 110 can use to determine where the users' devices are located.In these examples, when the monitoring service 110 determines that adevice is at, for example, a “home” location and has not moved for aperiod of time during the initial tracking period and/or the primarytracking period, the monitoring service 110 can determine that theperson associated with the device may not be carrying the device.

Alternatively or additionally, in some examples, when an attendee'sdevice has been stationary for a period of time, or if the device'slocation during the initial tracking period or the primary trackingperiod indicates that the device is moving away from the event location102, the monitoring service 110 may determine that the person associatedwith the device may not going to the event. In these examples, themonitoring service 110 can relay information such as “may not beattending” or “may not be carrying device” in the tracking data for thisperson. In some examples, the monitoring service 110 may push a reminderto the potentially non-attending user to request further informationfrom the user. In these examples, the user could send a quick reply suchas “not attending” or “delayed but coming” among other messages. Suchinformation could then be displayed to others attending the event. Invarious examples, the monitoring service 110 can attempt to determinewhether the potentially non-attending user has viewed the remindernotification. For example, the reminder can be pushed to a softwareapplication executing on the user's computing device, such that, whenthe user taps on or otherwise selects the reminder, the softwareapplication receives a notification, which the application can send tothe monitoring service. Alternatively or additionally, the reminder canappear in a notifications list provided by the computing device'soperating system, and when the user “swipes” or otherwise removes thereminder from the notifications list, the software application canreceive a notification from the operating system. In these and otherexamples, determining whether a user responds to a reminder can furtheraid the monitoring service in determining whether the person is not inpossession of the computing device.

In various examples, the software application provided by the monitoringservice 110 can provide an interface that can enable users to sendmessages only to invitees to an event, and/or only to attendees to theevent. This interface can enable users to provide updates about theevent or about themselves, such as indicating a late or early arrival, adecision not to attend, or other information. In some examples, theinterface can provide short messages that only require one action (e.g.,activating a user interface element by clicking or tapping the element)to be sent. Such messages can include, for example, “running late,” “bethere in five minutes,” “I'm on my way,” “stuck in traffic,” or similarmessages. In various examples, the application can enable users toprogram custom messages. In some examples, a group chat canautomatically be generated for each event. A group chat, which can alsobe referred to as a chat room, would allow users to share text messages,emojis, gifs, images, videos, or other electronic communications, amongother examples. In some examples, the monitoring service can beconfigured to purge communications generated in the event-specific chatwhen data for the event is purged.

In some examples, the monitoring service 110 may alternatively oradditionally receive tracking information from a data service. The dataservice may be able to obtain geolocation data from user devices, aswell as other data. The data service may provide an ApplicationProgramming Interface (API) through which an online service such as themonitoring service 110 can obtain the data. To obtain the data, themonitoring service 110 may need information such as a user identifier, adevice's Media Access Control (MAC) address, International MobileEquipment Identity (IMEI), Electronic Serial Number (ESN), MobileEquipment Identifier (MEID), and/or an authentication token authorizingthe monitoring service 110 to obtain the data on a user's behalf. Thedata that may be available from the data service can include, forexample, a device's location, a device's distance from an event location102, a device's rate of travel, a device's route when the device isbeing used to navigate to the event location 102, the manner in whichthe device is traveling (e.g., by train, by car, by bicycle, on foot,etc., which may be obtained from the navigation data), whether thedevice is “at home,” “at work,” or at another location designated by auser, and/or other data that can be used by the monitoring service 110to determine when or if the device will arrive at the event location102.

As noted above, the monitoring service 110 intends to provide trackingof computing devices only in relation to a particular event. Thus, at aspecified time after the start or end of the event, the monitoringservice 110 will delete the tracking data obtained for each device. Thetracking data will no longer be relevant, and deletion of the datasatisfies privacy and security concerns that any of the attendees to theevent may have.

FIG. 2 is a diagram illustrating an example of an event monitoringsystem 200. In various examples, the event monitoring system 200includes a monitoring service 220 that enables tracking of computingdevices, such as the computing device 210 illustrated in the example. Invarious examples, the monitoring service 220 can communicate with thecomputing device 210 over a network 250, which can include privatenetworks and/or public networks such as the Internet. In some examples,the monitoring service 220 can optionally communicate over the network250 with a data service 252 that can provide data about the computingdevice 210.

The computing device 210 of this example can include various types ofelectronic devices that include a microprocessor capable of executinginstructions of computing code, memory for storing the instructionsand/or other data, and network capability, such as a wired or wirelessnetwork card and/or a cellular antenna. Examples of such electronicdevices include laptop computers, desktop computers, tablet computers,smart phones, personal digital assistants, smart watches, digitaleyeglass systems, computing systems mounted into cars and othervehicles, and others.

In various examples, the computing device 210 can include hardware andsoftware that enable the computing device 210 to interact with themonitoring service 220 and to be tracked. For example, the computingdevice 210 can include a calendar application 212 through which a usercan generate calendar events and a monitoring application 214 thatinterfaces with the monitoring service 220. The computing device 210 canalso include one or more location devices 216 that can determine thecomputing device's location, and that produce location data 218.

The calendar application 212 can be a standalone application, such asGoogle Calendar or Apple Calendar, and/or can be integrated into anotherapplication, such as Outlook or a mobile application. Alternatively, thecalendar application 212 can be a web-based calendar that is accessiblethrough a web browser. In various examples, multiple calendarapplications may be available on the computing device 210. In someexamples, the calendar application 212 can aggregate calendar data fromdifferent calendar applications into the same interface. In someexamples, the calendar application 212 can receive calendar data form acalendar feed; that is, an interface through which calendar informationfrom other calendars can be provided to the calendar application 212. Inthese examples, the other calendars can be, for example, the calendarsof users other than the user of the computing device 210.

Using the calendar application 212, a user can set up a new calendarevent, including inviting users to join the event. The calendar eventcan be, for example a work-related meeting, a family gathering, a party,a dinner, a meeting for coffee, a concert, and so on. In some examples,the calendar event can be recurring, such as a monthly meeting or weeklysoccer practice. In some examples, the invitees to an event may begenerally the same for each recurrence of the event, such as when theevent is a book club meeting. In some examples, an event may be part ofa series of events where the approximately the same people will beattending each time. For example, the series of events can be practiceand/or games for a sports team.

The monitoring application 214 can enable a user to register calendarevents with the monitoring service 220 and/or to view tracking data whentracking is enabled for an event. In some examples, the monitoringapplication 214 can be linked to the calendar application 212, so thatwhen the user generates a new calendar event in the calendar application212, the monitoring application 214 can detect the new event. To detectthe new event, the monitoring application 214 can, for example, have abackground process or callback that detects when a calendar file isupdated on the computing device 210 and/or when calendar data isuploaded from the computing device 210 to a network location for storingthe calendar data. In some examples, the user can link specificcalendars to the monitoring application 214, so that any event added tothe linked calendar is registered for monitoring. In some examples, themonitoring application 214 may ask the user whether the user wants toregister an event for monitoring each time the monitoring application214 detects a new event.

In various examples, the monitoring application 214 and/or the calendarapplication 212 can send calendar event data to the monitoring service220 to register the event for monitoring. In various examples, themonitoring service 220 can be implemented using various softwareprocesses executing on or more server computers 222. The softwareprocesses can include, for example, an event generation process 230, anuser management process 232, an event monitoring process 234, and a datapurge process 236, among others. The monitoring service 220 can furtherinclude one or more data stores to store data such as user data 224 andevent data 226, among other data. The data stores can be implementedusing, for example, hard drives, solid state drives, or another form ofnon-volatile storage memory.

The server computers 222 on which the processes execute can be computingdevices that include one or more processors capable of executing programinstructions and memory for storing the program instructions. The servercomputers 222 and the data stores can, for example, be housed in a datacenter and/or provided as a service from a data center.

The event generation process 230 can register new events for monitoring.For example, when the monitoring service 220 receives data about acalendar event, the monitoring service 220 can determine the parametersof the event, including the date, start time, the location, and/or theusers invited to join the event, among other parameters. In variousexamples, the event generation process 230 can store the parameters ofthe calendar event in the data store for the event data 226. Asdiscussed further below, the event generation process 230 can receivedata about a calendar event in different ways, such as by email, in adata packet from the monitoring application 214, and/or using an API toa calendar service or a calendar feed, among other methods.

The user management process 232 can manage the user data 224, includingdetermining whether a user invited to join an event is registered withthe monitoring service 220, sending invitations when a user is notalready registered, associating registered users with the users listedas invited to join a calendar event, and/or maintaining the status ofinvitee users (e.g., whether a user has accepted, declined, or notresponded). In various examples, the user management process 232 canreceive a list of invitee users from the event generation process 230.The list may include, for example, user identifiers, email addresses,social media handles, or some other form of identification for theinvitee users. In these and other examples, the user management process232 can search the user data 224 to match the user identifiers withentries for registered users. The user management process 232 can thenassociate the registered users with the calendar event, and store theassociation with the calendar event's data in the data store for theevent data 226. In various examples, the user data 224 can also includedata identifying each invitee users' registered device or devices, whichcan also be associated with the calendar event.

The monitoring service 220 can enable the event monitoring process 234when the monitoring period for a calendar event starts. As noted above,the monitoring period can start a certain number of minutes or hoursbefore the start of the event or at the start of the event. As alsonoted above, the monitoring period can include an initial monitoringperiod, during which the event monitoring process 234 determines aninitial location and estimated time of arrival of each attendee user'sregistered device, and during which tracking data for each device is notyet provided. The monitoring period can end at the start of the event,some number of minutes after the start of the event, at the end of theevent, some number of minutes after the end of the event, when allattendees arrive, or at some other time that is related to the event. Insome examples, monitoring can stop for some or all attendees when eacharrives at the event location. In some examples, a combination offactors can determine when the monitoring period ends, such as all ofthe attendees arriving or else a number of minutes after the start ofthe event being reached. In some examples, during the monitoring period,a user can indicate “not attending” and monitoring for that user willstop immediately.

During the monitoring period, the event monitoring process 234 cangather data about each device being monitored. For example, the eventmonitoring process 234 can obtain the location data 218 that isgenerated by a computing device's location devices 216. The locationdata 218 can include the computing device 210 location at a givenmoment, and by obtaining the location data 218 at intervals of time, theevent monitoring process 234 can determine the computing device's rateof movement. From this and other data, the event monitoring process 234can compute the computing device's estimated time of arrival at an eventlocation.

In some examples, the event monitoring process 234 can obtain trackinginformation for the computing device 210 from a data service 252. Thedata service 252 may itself obtain location data 218 from the computingdevice 210 for various reasons, such as to provide navigation data(e.g., directions to an event), to provide location based services suchas weather or news, or for other reasons. In various examples, the dataservice 252 can provide the location data 218 to other services, such asthe monitoring service 220. In most cases the data service 252 onlyprovides the location data 218 when a user associated with the data hasprovided authorization for a services such as the monitoring service 220to receive the data.

When the event monitoring process 234 receives tracking information fromthe data service 252, in some examples, the event monitoring process 234can determine the computing device 210 location and estimated time ofarrival. In some examples, the data service 252 can provide additionaldata, such as route information, traffic information, train schedules,and other data, that can make the tracking data for the computing device210 more accurate. In some examples, the data service 252 can itselfprovide an estimated time when the computing device 210 will reach anevent location. In some examples, external services such as thoseprovided by Google Maps Platform can be called on to request a user'sestimated time of arrival, routing, or other geolocation data.

In various examples, the event monitoring process 234 can output thecomputing device's location and/or estimated time of arrival for viewingusing the computing device 210 and the devices of other users that havebeen granted access to the data. The monitoring application 214, forexample, can include a user interface that can display a location and/orestimated time of arrival. In some examples, the event monitoringprocess 234 pushes this tracking data to the monitoring application 214,so that the monitoring application 214 can indicate that the monitoringperiod is active and that updated tracking information is available. Insome examples, the monitoring application 214 pulls the tracking datafrom the event monitoring process 234 whenever the monitoringapplication 214 is launched.

In various examples, during the monitoring period, the monitoringapplication 214 can also enable other data to be available. For example,a chat session may be available, through which attendee users can sendmessages to one another. In some examples, chat or instant messaging forinvitee and attendee users can also be available before the monitoringperiod, so that users can discuss the event. As another example, duringthe monitoring period, the monitoring application 214 can enable a menuof quick messages that can be sent with one click or tap, for situationswhere a user needs to provide an update about the user's status (e.g.,running late) and is not free to type a message.

The monitoring service 220 can enable the data purge process 236 at theend of the monitoring period, or at a certain time thereafter. The datapurge process 236 can delete from the event data 226 all data related toa specific event, including the parameters of the event, anycommunications generated through a group chat initiated for the event,and any tracking data obtaining during the monitoring period for theevent. No history of events or tracking data is kept by the monitoringservice 220, because it is assumed that this data is no longer neededonce an event is over. Purging the data can also satisfy safety,security, and privacy concerns of the people using the monitoringservice 220.

FIG. 3 is a diagram illustrating an example of a process 300 forregistering a calendar event with a monitoring service 320. The exampleprocess 300 can include steps performed by a computing device 310, suchas a smartphone, a tablet computer, or another portable electronicdevice, and a monitoring service 320, such as the monitoring serviceillustrated in FIG. 2.

In the example of FIG. 3, a calendar event is generated using a calendarapplication 312 executing on a user's computing device 310. Using thecalendar application 312, the user can, at step 330, specify parametersof the event. The parameters can include, for example a date or datesfor the event, a start time, an end time, and/or a location for theevent, among other parameters. The user generating the calendar eventmay be considered the owner of the event; that is, a user with theability to change the event, invite other users, monitor invitationacceptances and rejections, and/or take other actions that invitee usersmay not be able to take. In some cases, another user may be the owner,and/or there may be multiple owners. Having obtained the eventparameters, the monitoring service 320 can store the parameters in anevent data database.

At step 332, the user can invite other users to join the event. Thecalendar application 312 can enable the owner user to, for example,specify email addresses for the other users, to select user identifiersor names from a list, and/or to search for users. In some examples, thecalendar application 312 can enable the owner user to invite anotheruser by specifying the invited user's email address. In some examples,the calendar application 312 may limit the users who can be invited. Forexample, the owner user may only be allowed to invite users from withinthe user's contacts list or own organization.

At step 334, in addition to inviting users to join the event, the owneruser can also invite the monitoring service 320 to join the event. Themonitoring service 320 can be invited, for example, using an emailaddress that is provided by the monitoring service 320 for this purpose.In this example, the monitoring service 320 can be added as an inviteein the same manner as users who are invited to join the event. As aninvitee, the monitoring service 320 can also receive updates or changesto the event. For example, when a change is made to the event thecalendar application 312 can send notifications to each of the inviteeusers, including the monitoring service 320.

At step 336, the user can add the event to the user's calendar, whichcauses the event to be generated and data for the event to be stored ina calendar file or elsewhere. At step 336, the calendar application 312may also send a notification of the calendar event to each of theinvitees added at step 332 and step 334. The notification can include alink or graphical user element that enables an invitee user to respondto the invitation in the affirmative or in the negative. In someexamples, when an invitee user activates a link or button, the inviteeuser's own computing device can send an email back to the owner user toindicate acceptance, rejection, or possibly a “tentative” or “maybe”status. In some examples, an invitee user's response may be hidden fromthe owner user, and may be received by the calendar application 312,which can maintain each invitee user's status. In some examples, when aninvitee user activates a link or button from the notification, theinvitee user may be taken to a calendar application executing on theinvitee user's own computing device or to a web site, where the inviteeuser can indicate acceptance, rejection, or an uncertain status.

In various examples, a notification inviting users to join the calendarevent is also received by the monitoring service 320. At step 360, themonitoring service 320 can use the notification to determine the eventparameters. Step 360 can be performed, for example, by an eventgeneration process executing on a server computer. In some cases, thenotification includes the event parameters, for the convenience of theinvitee users. In cases where the notification requires activating alink or graphical element to obtain the event parameters, the monitoringservice 320 can include automated processes or “bots” that can activatethe link or graphical element to activate the application or websitefrom which the monitoring service 320 can obtain the event parameters.

In various examples, the event notification can also include a list ofother users invited to attend the event. At step 362, the monitoringservice 320 can determine which of the other invitees are members of themonitoring service 320 and which are not. Step 362 can be performed, forexample, by a user management process executing on a server computer.The user management process can, for example, match user identifiers inthe notification against user identifiers for registered users, whichare stored in a user database.

For invitee users who are not found in the user database, at step 364,the monitoring service 320 can send an invitation to join the monitoringservice 320 to these non-registered users. Step 364 can be performed,for example, by the user management process. In various examples, themonitoring service 320 may require registration because registering withthe monitoring service 320 indicates consent to be tracked. Theinvitation to join can be in the form of an email, a text message, aninstant message, or another form of electronic communication.

In some examples, at step 360 the monitoring service 320 may determinethat no users have been invited to the calendar event. In theseexamples, the monitoring service 320 may determine to not register thecalendar event, since the owner/administrator of the event is not likelyto find it necessary to monitor only the owner/administrator's ownlocation. In these examples, the monitoring service 320 may exit theprocess 300 after step 360.

At step 368, the monitoring service 320 can monitor registration by newusers. Step 368 can be performed, for example, by the user managementprocess. New users can register, for example, by responding to theinvitation sent by the monitoring service 320, by downloading themonitoring service's application onto a computing device and configuringa user identifier with the application, through website provided by themonitoring service 320, or through another method. In some examples,when a user registers with the monitoring service 320 in connection witha particular calendar event, the user can, at the same time, consent tobeing tracked in relation to the event. In some examples, the user canseparately indicate consent to be tracked in relation to the event.

At step 366, the monitoring service 320 can monitor invitationacceptances for registered users. Step 366 can be performed, forexample, by the event generation process. In some examples, themonitoring service 320 can send the registered invitee users anotification that is separate from the calendar notification, whichrequests the invitee user to indicate whether the invitees want to betracked and/or want access to the tracking data of other users. In someexamples, the monitoring service 320 can be configured to requireinvitee users to accept being tracked. In some examples, the monitoringservice 320 can be configured to make access to the tracking data for anevent contingent on an invitee user accepting being tracked. In someexamples, the monitoring service 320 can be configured so that aregistered invitee user who accepts the invitation to join an event willautomatically be tracked, and/or will automatically have access to thetracking data for the event.

In some examples, step 366 can include receiving updated informationabout the calendar event from the calendar application 312. The updatedinformation can include invitee users' acceptance and rejectionstatuses, as well as updated parameters for the event. In some examples,at step 366 the monitoring service 320 may query the calendarapplication 312 for updated information, for example through an APIprovided by the calendar application 312.

At step 370, the monitoring service 320 can update the event data for acalendar event with the results of step 366 and step 368. Step 370 canbe performed, for example, by the event generation process or an eventmonitoring process executing on a server computer. Updating the eventdata can include reading the event data from an event data database andwriting updated to the event data database. The updated data can includeupdated statuses for invitee users (e.g., whether a user has accepted ordeclined to join the event), changes to which users have been invited,changes to the event time, date, and/or location, and other changes.

FIG. 4 is a diagram illustrating another example process 400 forregistering an event with a monitoring service 420. The example process400 can include steps performed at a computer device 410, which can be aportable electronic device, and at a monitoring service 420, such as themonitoring service illustrated in FIG. 2.

In the example of FIG. 4, the event is generated using a monitoringapplication 414 that is executing on a user's computing device 410. Themonitoring application 414 can be provided by the monitoring service420, as an interface to the monitoring service 420. The monitoringapplication 414 may have functionality for generating calendar eventsthat is similar to the functionality of a calendar application,including displaying a calendar for selecting the date of the event,displaying a map for determining the event's location, being able toselect a start and end time for the event, and so on.

In addition to enabling a user, at step 430, to specify the event'sparameters, the monitoring application 414 can enable the owner user to,at step 432, invite users to join the event. In some examples, themonitoring application 414 can be linked to a contacts list 440 that isavailable on the computing device 410. In these examples, the owner usercan access the contacts list 440 to identify users to invite. In someexamples, the monitoring application 414 can, additionally oralternatively, maintain a separate contacts list, which identifies usersthat are registered with the monitoring service 420. In some examples,the monitoring service 420 can identify users in the owner user'scontact list that are registered with the monitoring service 420, andcan augment the contacts list 440 by indicating a user's registrationstatus.

Once the owner user has specified users to invite, the owner user can,at step 436, add the new calendar event to a calendar. In variousexamples, the monitoring application 414 can communicate the calendarevent to a calendar application 412, which can add the event to acalendar maintained by the calendar application 412. In these examples,the event can be added to an existing calendar. In some examples,because the event was added to the calendar through the monitoringapplication 414, the event will be monitored, while events that were notadded to through the monitoring application 414 will not be monitored.In various examples, when the event is added to the user's calendar, themonitoring application 414 or the calendar application 412 can sendnotifications to the invitee users to inform these users about theevent, and request a reply to the invitation to join the event.

When the event is added to the owner user's calendar through themonitoring application 414, the monitoring application 414 can also sendinformation about the event to the monitoring service 420. Theinformation can include the parameters of the event and a list of userswho have been invited to the event. At step 462, the monitoring service420 can identify invited users who have previously registered with themonitoring service 420 For invitee users who have not previouslyregistered, at step 464 the monitoring service 420 can send these usersan invitation to register with the monitoring service 420. At step 468,the monitoring service 420 can monitor responses to the invitation toregister, and can register new users, and possibly also receive anindication from the new users as to whether these users are going tojoin the event.

At step 466, the monitoring service 420 can monitor invitationacceptances from registered users. In some examples, invitee users canaccept, decline, or indicate a “tentative” or “maybe” status through thecalendar application 412, which can transmit this information to themonitoring service 420. In some examples, the invitee users can indicatea status through email, text message, instant message, or some otherform of digital communication. The invitee user's status can be receivedby the calendar application 412 when the invitee user received anotification from the calendar application 412, or by the monitoringapplication 414 when the invitee user received a notification from themonitoring application 414. When the reply is received at the calendarapplication 412, the monitoring application 414 may be able to obtainthe reply, for example, by querying the calendar application 412 usingan API provided by the calendar application 412. Alternatively oradditionally, the owner user's calendar may be linked to the monitoringapplication 414, so that the monitoring application 414 can detect anychanges to the calendar file that stores the calendar's data.

At step 470, the monitoring service 420 can update the event data withinformation obtained at step 466 and 468. In various examples, themonitoring service 420 can update the event data each time themonitoring service 420 receives an update about the event. In someexamples, the monitoring service 420 can periodically check whether anyupdated information is available for the event, for example by queryingthe monitoring application 414 or instructing the monitoring application414 to query to the calendar application 412.

FIG. 5 is a diagram illustrating another example process 500 forregistering a calendar event with a monitoring service 520. The exampleprocess 500 can include steps performed at a computing device 510, whichcan be a portable electronic device, and at a monitoring service 520,such as the monitoring service illustrated in FIG. 2.

In example of FIG. 5, a user can, at step 530, specify the eventparameters for an event using a calendar application 512 that isexecuting on a computing device 510. At step 532, the user can alsoinvite users to join the event through the calendar application 512. Inthis example, the calendar to which the event is added can be linked toa monitoring application 514, so that, when, at step 536, the user addsthe event to the user's calendar, the monitoring application 514 isnotified.

“Linking” or associating a calendar with the monitoring application 514means that the monitoring application 514 can read the data for thecalendar, which may be stored in structured format in a file or may beavailable from a calendar feed, and/or can detect when data for thecalendar is changed. In some examples, the calendar application 512 canpush new or modified calendar data to the monitoring application 514. Insome examples, the monitoring application 514 can have a callbackfunction that triggers whenever the calendar file is modified. In someexamples, the monitoring application 514 periodically checks thecalendar file to see if the calendar file has been modified. In theseexamples, the monitoring application 514 can, for example, check thecalendar file's modification time to determine whether the calendarapplication 512 has changed the calendar file.

At step 542, the monitoring application 514 can detect that an event hasbeen added to the owner user's calendar, and can send information aboutthe event to the monitoring service 520. At step 560, the monitoringservice 520 can determine the event parameters, including the event'sdate, start time, end time, location, and/or a list of users identifiedto join the event. At step 562, the monitoring service 520 can identifyinvited users who have previously registered with the monitoring service520 For invitee users who have not previously registered, at step 564the monitoring service 520 can send these users an invitation toregister with the monitoring service 520. At step 568, the monitoringservice 520 can monitor responses to the invitation to register, and canregister new users, and possibly also receive an indication from the newusers as to whether these users are going to join the event.

At step 566, the monitoring service 520 can monitor invitationacceptances from registered users. In some examples, the monitoringapplication 514 can detect changes to the linked calendar. In theseexamples, the monitoring application 514 can determine what the changeswere, and can send these changes to the monitoring service 520. Thechanges can include, for example, changes to the date or time of theevent, changes to the location, changes to the list of invited users,and/or responses from invited users, among other changes.

At step 570, the monitoring service 520 can update the event data withinformation obtained at step 566 and 568.

FIG. 6 is a diagram illustrating an example process 600 a monitoringservice 620 can perform when monitoring a calendar event. The exampleprocess 600 can be performed by a monitoring service 620, such as themonitoring service illustrated in FIG. 2, and can involve, asillustrated in FIG. 6, data being transmitted to a computing device 610.

At step 672, the monitoring service 620 can determine the monitoringparameters for the calendar event. The monitoring parameters can includea listing of the devices that are to be tracked, the devices to whichthe tracking data is available, and the monitoring period. The devicesto be tracked can be determined from a list of users that were invitedto join the calendar event. For example, the monitoring service 620 candetermine which users accepted the invitation to join, and for theseusers, add devices associated with the users to a list of devices totrack. The devices to which tracking data is available can include someor all of the devices that are to be tracked. In some cases, fewer thanall the devices that are tracked can receive the tracking data, forexample because some users have restricted visibility of the trackingdata for their devices.

The monitoring period is the time over which the monitoring service 620tracks the devices that are to be tracked and/or provides access to thetracking data. In some examples, the monitoring service 620 determinesthe monitoring parameters when the event is registered. Alternatively oradditionally, the monitoring service 620 may determine one or more ofthe monitoring parameters at a point in time between when the event isregistered and when the event is near to starting, such as a day beforethe start of the event or two hours before the start of the event. Forexample, the monitoring service may determine the monitoring periodstart time and end time, and close to the start time (e.g., a half hourbefore, fifteen minutes before, or some other interval of timebeforehand) determine the devices that are to be tracked. In someexamples, the monitoring service 620 can continue to update the devicesto be tracked and/or the devices that can receive the tracking data oncethe monitoring period has started. For example, the monitoring service620 can determine that a user's status has changed from “invited” to“accepted” within the monitoring period, and can subsequently add theuser's device to the list of devices being tracked.

In some examples, the monitoring period can also include an initialmonitoring period, during which the monitoring service 620 beginstracking devices, but does not yet make the tracking data available.During the initial monitoring period, the monitoring service 620 canestablish a location for each device being tracked, and can make aninitial calculation of each device's estimated time of arrival. Theestimated time of arrival can be made more accurate, for example, byusing a device's location information over the initial monitoring periodto determine the device's direction of travel, mode of travel, and/orrate of travel, among other time-based information. Before thisinformation is collected, the monitoring service 620 may only have thedevice's instantaneous location, and thus may only be able to determinea very rough estimate of the device's time of arrival. Additionally, theevent parameters and/or display preferences associated with the devicemay not allow for the device's instantaneous location to be visible. Insome examples, a device's location data may include, at the timetracking data is obtained for the device, information such as thedevice's direction of travel, mode of travel, and/or rate of travel, inwhich case the initial monitoring period may not be needed.

At step 674, the monitoring service 620 can determine that the start ofthe monitoring period has been reached, and can start monitoring. Invarious examples, the start of the monitoring period is relative to thestart of the event, such as a certain number of minutes before theevent, at the start of the event, or a certain number of minutes afterthe start of the event.

Once the monitoring service 620 has enabled monitoring, then, at step676, the monitoring service 620 can determine a status for each attendeeuser for the event. Determining an attendee user's status can include,for example, determining the location of the user's device, determiningthe device's location relative to the event location, determining thedevice's rate of travel, and any other information that can be used toestimate when the device will arrive at the event location. In someexamples, the monitoring service 620 can obtain location informationfrom the user's device. In some examples, the monitoring service 620 canobtain location information and/or other information about the user'sdevice from a data service.

Once the monitoring service 620 has obtained tracking information for auser's device, the monitoring service 620 can determine an estimatedtime at which the device will arrive at the event location. At step 678,the monitoring service 620 can update each attendee user's status withthe estimated time of arrival. Updating the user's status can alsoinclude updating the current location of the user's device and/or thecurrent distance of the user's device from the event location. In someexamples, updating the user's status can also include updating theuser's route to the event location, where the route can be indicated bythe user, can be inferred by the monitoring service 620, and/or can beprovided by a data service.

In various examples. the attendee users' status can be displayed, as atstep 644, in a monitoring application 614 that users can execute on acomputing device 610. In some examples, determining attendee users'status, at step 676, can also include determining the trackinginformation to display at step 644. For example, an attendee user mayhave only enabled display of the user's estimated time of arrival at theevent location, and may have disabled display of any locationinformation. As another example, the attendee user may have enableddisplay of the user's distance from the event, but not the attendeeuser's exact location. As another example, the attendee user may haveenabled display of the user's exact location, as provided by the user'sdevice. In some examples, the owner of the event can set the degree ofdetail of the tracking data that can be viewed the monitoringapplication 614.

In some examples, once an attendee user has reached the event location,the monitoring service 620 can so determine at step 676, and can displaythis fact in the monitoring application 614. In some examples, thecomputing device 610 can stop tracking an attendee user once the userhas reached the event location. In some examples, the monitoring service620 can continue tracking an attendee user, for example if the owner ofthe event has configured the monitoring service 620 to keep trackingattendee users and/or if the attendee user has requested for tracking tocontinue.

In various examples, the monitoring service 620 returns to step 676 fromstep 678 after an interval of time, such as after 30 seconds, after oneminute, after five minutes, or after another interval of time. At step676, the monitoring service 620 can acquire more current trackinginformation for each attendee user, and can determine an updated statusfor the attendee users. The monitoring service 620 can then return tostep 678 to update the attendee users' status that can be viewed in themonitoring application 614.

In some cases, some of the parameters of the event may be unspecified.For example, the event location may not have been specified when theevent was generated, and may not have been added by the time themonitoring period starts. In this example, the monitoring service 620may, before starting monitoring at step 674, query the owner of theevent to ask for an event location. Alternatively or additionally, insome examples the monitoring service 620 can be configured to assumethat the location of the owner user's device is the event location. Inthese examples, the owner user may be moving, such that the assumedevent location changes. In these examples, the monitoring service 620can dynamically update the attendee user's tracking data as the owneruser's location changes.

Once the end of the monitoring period has been reached, at step 680 themonitoring service 620 can disable further tracking of the attendeeusers' devices. The monitoring service 620 can then proceed to step 682,where the monitoring service 620 will delete the monitoring data andpossibly also any other data related to the event. For example, themonitoring service 620 can delete the data the monitoring service 620acquired at step 676 and the result of any computations executed on thisdata, including attendee user's distance from the event location, routeto the event location, and/or estimated or actual time of arrival at theevent. As a further example, the monitoring service 620 can delete theevent parameters, and remove the event from the monitoring service'sevent data base. As another example, the monitoring service 620 candelete communications generated by attendee users, for example throughan event-specific group chat provided by the monitoring service 620.

FIG. 7 is a diagram of an example timeline 700, which illustrates oneexample of a monitoring period relative to the timeframe of an event. Inthis example, the timeline 700 illustrates the activities of amonitoring service with respect to one event that has been registeredwith the monitoring service. As discussed further below, variations onthe illustrated timeline 700 are possible. FIG. 7 further illustratesthree devices 710 a-710 c that have been registered with the monitoringservice, and the activities the monitoring service takes with respect tothese three devices 710 a-710 c.

In the illustrated example, the event starts at time 706. The eventstart time can be recorded in a data entry in a calendar file, which amonitoring service can access to determine when the event will start.Alternatively or additionally, the monitoring service can include a datastore in which the monitoring service stores calendar events that are tobe monitored.

At a time 702 before the event start at time 706, the monitoring servicecan determine the event parameters. Time 702 can be a number of minutes,a number of hours, or a number of days before the start of the event.The event parameters can include a listing of the devices to be tracked.As an example, in the example of FIG. 7, a first device, Device-1 710 ais associated with a user that has accepted an invitation to join theevent (e.g., a status associated with the user indicates “accepted” orsomething similar). In this example, the monitoring service can, at time702, add Device-1 710 a to a list of devices for which the monitoringservice will collect tracking data. As a further example, a seconddevice, Device-2 710 b, is also associated with a user that has acceptedan invitation to join the event, and the monitoring service can also addDevice-2 710 b to the list of devices for which to collect trackingdata. As a further example, a third device, Device-3 710 c, isassociated with a user who was invited to join the event, but who eitherdid not accept the invitation or who did not respond (e.g., a statusassociated with the user is “invited” or “declined” or another statusother than “accepted”). In this case, though Device-3 710 c isassociated with a user who was invited to the event, the monitoringservice does not add the device to the list of devices to be tracked.

Also at time 702, the monitoring service can determine listing ofdevices that can receive the tracking data that is collected. Forexample, the event parameters can indicate that Device-1 710 a andDevice-2 710 b are both associated with users who have accepted theinvitation to join the event, and that these two devices thus canreceive the tracking data. The monitoring service can further determinethat Device-3 710 c should not receive any of the tracking data, due tothe user associated with this device having declined to join the eventor having not responded to the invitation.

At time 702, the monitoring service can further determine the monitoringperiod. The start of the monitoring period can be relative to the starttime of the event. In the example of FIG. 7, the monitoring periodstarts at a time 704, which is before the start time of the event. Inthis example, monitoring of the event has been configured so that eventattendees can see when other attendees are arriving, and/or where theother attendees are prior to the start of the event. In other examples,the monitoring period can start when the event starts or after the eventstarts. In these examples, monitoring of the event may have beenconfigured so that even attendees can locate one another after the eventhas started.

Also in the example of FIG. 7, the monitoring period stops at a time708, shortly after the start time of the event. In this example, the endof the monitoring period may have been configured to be at a fixed timeafter the start of the event, and/or when a condition is met (such ascertain attendees or all attendees arriving at the event location). Inother examples, the monitoring period can end at the start of the event,at the end of the event (not illustrated here), or after the end of theevent.

Having determined the monitoring period, the monitoring service can thenwait until time 704 is reached. Time 704 can be a few minutes, a fewhours, or a few days after time 702. Before time 704 is reached, themonitoring service will not be tracking any of the devices 710 a-710 c.The is, the monitoring service will not be collecting any tracking datafrom these devices 710 a-710 c, and will have no knowledge of thephysical or network locations of the devices 710 a-710 c. When time 704is reached, the monitoring service can activate tracking of Device-1 710a and Device-2 710 b, and will not activate tracking of Device-3 710 c.While tracking is activated, the monitoring service 620 can obtaintracking data for each of Device-1 710 a and Device-2 710 b, for examplefrom the devices and/or from a data service.

Once tracking is enabled, the monitoring service may also make thetracking data available to devices that the monitoring service hasidentified as being able to receive the data. For example, in theexample of FIG. 7, parameters for the event have configured themonitoring service to make the tracking data for both Device-1 710 a andDevice-2 710 b available. Making the data available can mean, forexample, that when either of the devices 710 a-710 b connect to themonitoring service, for example through an app executing on the devices710 a-710 b, the devices 710 a-710 b can receive the tracking data. Asanother example, when the tracking data is available, the monitoringservice may push (e.g., actively transmit) the tracking data to thedevices 710 a-710 b. When the data is pushed to the device, themonitoring service may also cause a notification to be generated on thedevice, to inform a user that updated tracking data is available.

As noted above, the event parameters can also indicate the degree ofdetail of the tracking data that each device 710 a-710 b should receive.For example, the event parameters can indicate that the tracking datafor Device-1 710 a should be available to all devices that can receivethe tracking data, which, in this example, includes only Device-1 710 aand Device-2 710 b. The event parameters may further indicate that thetracking data for Device-2 710 b is restricted, meaning that themonitoring service should only give access to a limited amount of thetracking data for this device. For example, the event parameters mayindicate that only an estimated time of arrival for time Device-2 710 bshould be available, or only an approximate distance of Device-2 710 bfrom the event location. Alternatively, the event parameters mayindicate that the tracking data for Device-2 710 b should be hidden fromDevice-1 710 a. In various examples, the restricted availability of thetracking data for Device-2 710 b can be configured by the userassociated with Device-2 710 b, by the event owner, and/or by anotheruser.

In various examples, between the start of the monitoring period at time704 and the end of the monitoring period at time 708, the monitoringservice can continuously or periodically (e.g., at intervals of five orten minutes, or another time interval) obtain updated tracking data foreach of Device-1 710 a and Device-2 710 b. The monitoring service canthen use the updated tracking data to update each device's locationand/or estimated time of arrival at the event location.

Once the end of the monitoring period is reached, at time 708, themonitoring service can stop collecting tracking data for the devicesbeing tracked, and can stop providing the tracking data to the devicesthat can receive the data. Once tracking is disabled, the monitoringservice will no longer have any information about the location of thedevices 710 a-710 b, and, consequently, will not be able to providelocation information for the devices 710 a-710 b to any devices.

At or after the end of the monitoring period, for example at a time 709,the monitoring service can further delete the tracking data obtainedduring the monitoring period, as well as any other data generated duringthe monitoring period (e.g., instant messages or chat messages, statusmessages, etc.). In some examples, the monitoring service may furtherdelete all information about the event as well, including when the eventoccurred, where the event was located, which users were invited, whichusers indicated an intention to attend, and which actually attended,among other information. User accounts with the monitoring service,however, and user profiles associated with the accounts may bepreserved, though the user's association with the event may be deleted.Time 709 may occur a few minutes after the end of the monitoring period(e.g., fifteen minutes, an hour, or some other amount of time).Alternatively or additionally, time 709 may occur on a scheduled basis.For example, the monitoring service may be configured to routinely(e.g., once a day, once a week, twice a week, etc.) delete trackingdata. In this and other examples, time 709 may occur on a periodicbasis.

The parameters that result in the example timeline 700 of FIG. 7 areassociated with a specific event. A different event can have differentparameters, that can result in a different timeline that involves thesame or different devices.

FIG. 8 includes a flowchart illustrating an example of a process 800 formonitoring a calendar event. The example process 800 can be implementedby one or more server computers of a monitoring service, such as themonitoring service illustrated in FIG. 2.

At step 802, the process 800 of FIG. 8 includes receiving inputcorresponding to a calendar data entry, the calendar data entry addingan event to a calendar file, such as a calendar data entry that includesan event start time, an event geolocation, and a user identifier. Theevent start time can include a date and/or a time. In various examples,the calendar data entry is for adding a new calendar event to thecalendar file. In some examples, the calendar data entry is receivedfrom a calendar application. For example, the input can be receivedusing an API associated with the calendar application. In some examples,the calendar data entry is received from a calendar feed. For example,the monitoring service can be a client of the calendar feed, and thusautomatically receive calendar data from the calendar feed. In someexamples, the input can be an email, and can be received at an emailserver of the monitoring service. In some examples, the input isreceived from an application executing on a computing device, such as auser device. In these examples, the application can be a program that ispart of the monitoring service.

The user identifier can identify a user that has been requested to jointhe calendar event. The user identifier can be associated with an entryin a database maintained by the monitoring service. The database canstore user accounts for users registered with the monitoring service. Insome examples, the entry for a user identifier can stored an associationwith a device, such as a smart phone, tablet computer, or other mobilecomputing device. In some examples, the entry can store an associationwith a calendar file or a calendar feed. In these examples, the calendarfile or calendar feed is one that is used by the user for which theentry is maintained. For example, the calendar can be the user's Googleor Outlook calendar. In some examples, the entry can store an emailaddress. In these examples, the email address can be used to request forthe user to join the calendar event. For example, the request can besent to the email address.

In some examples, an entry for a user can store a list of identifiers ofother users who can or cannot see the monitoring status of the user. Forexample, the entry can include a list of users who are “blocked” fromseeing the user's monitoring status as determined for a particular eventor for any event. The users can be identifier by a user identifier withthe monitoring service, a user identifier for another service (e.g., aGoogle identifier, a social media identifier, etc.), an email address, aphone number, a first and/or last name, or some other identifier.

In some examples, an entry for a user can store a visibility setting. Inthese examples, the visibility setting can control display of the user'smonitoring status on the devices of other users. For example, thevisibility setting can indicate whether a high level of tracking detailshould be displayed for the user (e.g., an exact geolocation), anintermediate level of detail (e.g., an approximate distance from theevent location), or a low level of detail (e.g., an estimated arrivaltime and no location information). Additionally, the visibility settingcan indicate the level of detail that other users can see. For example,for one user (e.g., a user account used by a spouse), a user may want ahigh-level of tracking detail provided, while for another user (e.g., auser account of a co-worker), the user may want an intermediate level oftracking detail provided.

In some examples, the process 800 can further include determiningwhether the user identifier is associated with an entry in the userdatabase. In various examples, to use the monitoring service, a userregisters with the service. To determine whether the user has previouslyregistered, the monitoring service can check whether the service's userdatabase has an entry for the user. The user can be identified, forexample, by a user identifier, an email address, a social media handle,a phone number, or another identifier. The process 800 can furtherinclude generating, when the user identifier is not associated with anentry, a request to be added to the database, and transmitting therequest using contact information associated with the user identifier.The contact information can be, for example, an email address, a phonenumber, or another form of digital contact information. The request caninclude information about the monitoring service and information abouthow to register with the monitoring service and/or a link forregistering. When a user registers with the monitoring service, themonitoring service can generate a new entry for the user, and add thenew entry to the user database. In various examples, when the userregisters, the user can designate a computing device that can be trackedwhen tracking is enabled, and the monitoring service can storeidentification information for the computing device (e.g., a MACaddress, an IMEI number, or another identifier) in the user's databaseentry.

In various examples, the process 800 can further include receiving inputcorresponding to a response to the calendar event. The input canindicate whether a user has accepted the request to join the calendarevent, rejected the request, has responded “tentative,” “maybe,” or“uncertain,” and/or has only viewed the request without responding. Inthese examples, the process 800 can further include modifying the statusassociated with the user identifier based on the response. Beforemodification, the status an indicate, for example, “invited,” and aftermodification can indicate “accepted,” “declined” or otherwise notattending, “tentative” or otherwise uncertain, or can still be only“invited” but indicate that the user has at least viewed the request.

In various examples, the calendar data entry received at step 802 caninclude a plurality of user identifiers, each corresponding to a userthat has been requested to join the calendar event.

At step 804, the process 800 includes, at a first point in time relativeto the event start time, obtaining tracking data for a device associatedwith the user identifier. In some examples, the tracking data isobtained from a geolocation data service. Alternatively or additionally,in some examples, the tracking data is obtained from the device. In someexamples, the tracking data includes a geolocation (e.g., a geographiclocation) for the device.

In some examples, the first point in time is before the event starttime. In these examples, an interval of time passes between the firstpoint in time and the event start time. In some examples, the firstpoint of time is at the event start time.

In some examples, the process 800 further includes determining an eventstatus associated with the user identifier, the event status indicatingthat a user associated with the user identifier has accepted a requestto be included in the event. In these examples, the process 800 canfurther include enabling, based on the event status indicatingacceptance of the request, obtaining of the tracking data. When a userhas not accepted a request to be included in the event, tracking adevice associated with the user will not be enabled. For example, theprocess 800 can include determining an event status for a second useridentifier, such as a second user identifier that is included in thecalendar data entry. In this example, event status for the second useridentifier can indicate that a user associated with the second useridentifier has declined a request to be included in the event. In thisexample, based on the event status indicating non-acceptance, obtainingof tracking data for the second user identifier is not enabled.

At step 806, the process 800 includes determining, using the trackingdata, an approximate geolocation of the device. The geolocation can bebased on GPS data for the device, cellular antenna data, network data,and/or other positioning data. As such, the accuracy of the device'sgeolocation can be dependent on the technology used to obtain thegeolocation. The geolocation can be an address on a map, a latitude andlongitude, coordinates, or another format for recording a location onthe globe.

At step 808, the process 800 includes determining, using the approximategeolocation, an approximate time difference between a current time and atime when the device will be at the event geolocation. In some examples,the approximate time difference is computed using a distance between thedevice and the event geolocation. In some examples, the approximate timedifference is computing use a rate of movement of the device.

At step 810, the process 800 includes updating a location statusassociated with the user identifier, the location status indicating theapproximate time difference. In some examples, the location status canindicate an amount of time until the device is to reach the eventgeolocation. In some examples, the status indicates a distance betweenthe device and the event geolocation. In some examples, the statusindicates a geolocation of the device. In some examples, the statusindicates a projected route of the device from a current geolocation ofthe device to the event geolocation.

In some examples, the process 800 can further include determining adisplay level associated with the user identifier, the display levelindicating an amount of detail of the location status. For example, thedisplay level can indicate a high degree of detail, an intermediatedegree of detail, or a low degree of detail. The process 800 can furtherinclude outputting the location status according to the display level.The location status can be output to a second device. The second devicecan be associated with a second user identifier, where the second useridentifier is also included in the calendar data entry. An event statusassociated with the second user identifier can indicate that a userassociated with the second user identifier has accepted a request to beincluded in the event. Outputting of the location status to the seconddevice enabled based on the event status of the second user (e.g., thatthe user has accepted the request).

In some examples, the process 800 can include enabling the second deviceto receive the event status associated with the user identifier. Inthese examples, the second device can retrieve the event status from themonitoring service. In some examples, the event status can be activelytransmitted (e.g., “pushed”) to the second device.

At step 812, the process 800 includes at a second point in time relativeto the event start time, disabling tracking of the device. In someexamples, the second point in time is at the event start time. In someexamples, the second point in time is after the event start time, suchas a few minutes after the event start time and/or when some or all ofthe attendee users arrive at the event geolocation. In some examples,the second point in time is at the end time associated with the calendarevent.

At step 814, the process 800 includes at a third point in time after thesecond point in time, deleting the tracking data. The tracking data thatis deleted can include any tracking data obtained between the firstpoint in time and the second point in time. In various examples, thelocation status associated with the user identifier, as determinedbetween the first point in time and the second point in time, is alsodeleted. In these and other examples, the location status has a nullvalue before the first point in time and is deleted at the third pointin time, so that the location status again has a null value.

In some examples, the process 800 can also include determining an eventstatus for a second user identifier, where the second user identifierwas also included in the calendar data entry. In these examples, theevent status for the second user identifier can indicate that a userassociated with the second user identifier has declined a request to beincluded in the event. In these examples, based on this event status,the second user identifier is not able to obtain the location statusassociated with the user identifier. Additionally, a device associatedwith the second user identifier will not be tracked between the firstpoint in time and the second point in time, such that no location datafor the device of the second user will be obtained.

As described above, it may be desirable to generate different calendardata entries for each user (host, invitee, or participant) in a calendarevent so that the user can have better information about the other usersparticipating in the event. In general, some calendaring applicationsshow an event subject, an event host or organizer, location information,and date and time details for a calendar event when a user is presenteda day, week, or longer view of their electronic calendar, but littleelse about the event. This may be appropriate for a user who is simplytracking their own appointments, but when two or more people are usingcalendaring applications to schedule meetings, events, phone calls, orthe like, presenting more information can be useful. Some calendaringapplications may present more information to a user upon “opening” orotherwise activating or viewing details associated with a calendar, butthis typically includes a list of invitees. If the user is the host orcreator of the calendar event entry, the user may be able to identifywhich invitees have accepted or declined the meeting invite.

Since calendaring applications generally only show a subset of calendarevent information to a host or recipient of calendar event data entry(which may be called a calendar meeting request, meeting invite, or thelike) use of customized subjects can allow for participant informationto be shown. As one example, it may be desirable for a calendaringapplication to present to a user a list of guests (i.e., invitees,participants, or attendees) and/or a number of guests so that the userhas more details upon a brief glance at their calendar.

This information can be included in a conventional calendar event dataentry, but not without potential for confusion. When the event subjectis shared by all, an event might either be given a generic subject(e.g., “Meeting to discuss presentation”) or include a generic list ofparticipants (e.g., “Meeting with Team B to discuss presentation”) orinclude all participants (e.g., “Meeting with Dave and Haley and Amandaand Richard to discuss presentation”). While this latter subject maycorrectly identify the participants, it does not change if one or moreparticipants declines or otherwise indicates they cannot or will notparticipate in the meeting. Moreover, each guest will see their ownname, which will make it either appear they are meeting with themselvesor with another person with their same name. Use of dynamic or customcalendar event subjects can overcome these issues.

FIG. 9 includes a flowchart illustrating an example of a process 900 forinitiating generation of custom calendar entries including custom eventsubjects. Process 900 may correspond to a process performed by acomputing device or server for collecting information relating to acalendar event and determining a type of calendar event to generate. Atblock 905, information about a type of calendar event is received, whichmay be or correspond to input received from a user by a server,processor, or computing device. Example information may include, but isnot limited to, an indicator of whether a calendar event is a hostcentric event or not, an indicator of whether the current user is thehost or not, an identifier for a user, or the like.

A Host Centric event may correspond to an event where the host isintended to be the only name visible to other guests. This situation mayarise in business settings, such as where a business or host is hostingan event and it is not necessary that the other guests know who oneanother are in the event subject, though this may still be useful forthe business or host. An example may be if a real estate broker (Ben) ismeeting to show two clients (Luca and Melissa) an apartment or house.The host may find it useful to know which clients the event is scheduledfor, but the clients may not need or desire to have each other's namesindicated in the event subject. In such a case, the base event name andconnector word could optionally be different, such as where the host'scustom event subject may be “Show Apartment to Luca and Melissa” andboth Luca and Melissa's custom event subject may be “View Apartment withBen.”

At block 910, the process determines whether the event is a Host Centricevent, as described above. If the event is not a Host Centric event,block 910 directs process 900 to block 915, where the core event name, aconnector, and a guest list may be received, which may be or correspondto input received from a user by a server, processor, or computingdevice. This information may be forwarded to block 940 for initiating aprocess for building a dynamic subject or name for the event.

If the event is a Host Centric event, block 910 directs process 900 toblock 920. At block 920, a distinction is made whether the current useris the host or not. This may allow for different core event names to beused for the host and the guests in a Host Centric event. If the user isnot the host, block 920 directs process 900 to block 925, where the coreevent name for the guest in a Host Centric event (a guest core eventname), a connector, and the host name may be received, which may be orcorrespond to input received from a user by a server, processor, orcomputing device. This information may be forwarded to block 940 forinitiating a process for building a dynamic subject or name for theevent.

If the user is the host, block 920 directs process 900 to block 930,where the core event name for the host in a Host Centric event (a hostcore event name), a connector, and the guest list may be received, whichmay be or correspond to input received from a user by a server,processor, or computing device. This information may be forwarded toblock 940 for initiating a process for building a dynamic subject orname for the event. In a Host Centric event, the guest list used forgenerating a dynamic subject or event name for the host may include theinvited guests, while the guest list used for generating a dynamicsubject or event name for the guests may include only the host.

FIG. 10 includes a flowchart illustrating an example of a process 1000for initiating building of a dynamic subject or event name. Process 1000may correspond to a process performed by a computing device or serverfor creation of or updating of calendar event data associated with acustom event subject for one or more users. Process 1000 may beperformed for each guest of a calendar event, including invitees, hosts,participants, etc.

At block 1005, calendar data entry information is received, which may beor correspond to input received from a user by a server, processor, orcomputing device. In some cases, this may correspond to informationobtained at blocks 915, 925, or 930 as part of process 900 depicted inFIG. 9. Example calendar data entry information includes, but is notlimited to a core or base event name, an identifier for a user, a guestlist, a language, an event start time, an event end time, a duration, alocation, or the like. As described above, users may accept or declinecalendar events, and a computing device, server, or processor mayreceive a communication indicating this RSVP information. For process1000, at block 1010, the process queries whether the current user hasdeclined the event. If the user has declined, the process completes atblock 1015 by generating a custom event subject that is just the coreevent name (e.g., “Meeting” or “Lunch”). This completion may beoptional, since a custom subject may not be needed for users that havedeclined to participate in the event.

For a user who has not declined to participate in the event (i.e., haseither accepted to participate in the event or has not yet indicatedtheir response), process 1000 proceeds to block 1020. At block 1020,users that have declined are removed from a working guest list used forgenerating a custom event subject, since these users do not need to beidentified as participating in the event At block 1025 the current userfor which process 1000 is currently operating to generate a custom eventsubject is also removed from the working guest list. In some cases,block 1025 may be optional and can be flagged as such by user preferencein the event a user indicates they want their own name listed in acustom event subject.

Process 1000 proceeds to block 1030, where a number of guests in theupdated working guest list is determined. At block 1035, the number ofguests is processed at a query to determine whether there are any otherusers participating in the event besides the current user. If the numberof guests is zero, meaning the current user is the only guest, thecustom event subject for the current user is generated at block 1040,such as by indicating only the core event name.

For indicating participation in the event by other users, a connectorword may be set. The connector word may be a preposition indicatingaccompaniment by others, such as “with” or “including”. Although theconnector word “with” is used in the examples described herein, otherconnector words may be used in place of “with”. The connector word maybe translated to the desired language indicated in the eventinformation, such as if a user's local settings or preferences indicatethey are using a language other than English.

At block 1045, a custom event guest list string is generated. The customevent guest list string may indicate all other guests, one or more otherguests, a subset of the guests, and/or a summary of guests notspecifically enumerated. Further details regarding generation of acustom event guest list string are provided below with respect to FIG.11.

In some circumstances, the custom event guest list string may be emptyor may be null. For example, in some embodiments, users that are notregistered with a particular calendaring application or system may nothave names associated for inclusion in the custom guest list string, sotheir names may be empty or null. If the custom event guest list stringis empty or null, block 1050 will direct process 1000 to block 1055, forgenerating a custom event subject that is just the core event name. Itwill be appreciated that blocks 1050 and 1055 may be optional. Forexample, the system may be configured to never use null or empty guestnames and instead use an email address, identifier, phone number, orother information used for inviting a guest with no registered name inplace of the guest's name.

When the custom event guest list string is not empty or null, block 1050will direct process 1000 to block 1060, where a custom event subject isgenerated using the core event name, the connector word, and the customevent guest list string.

FIG. 11 includes a flowchart illustrating an example of a process 1100for generating a custom guest list string for use in a custom eventsubject. Block 1105 shows information used for generating a custom guestlist string, which may be optionally received as input or be includedwith or derived from a calendar data entry. Example information used forgenerating a custom guest list string includes, but is not limited to alanguage, a guest list, which may be a working guest list, a number ofguests in the working guest list, or the like.

At block 1110 the number of guests other than the current user, whichmay be the number of guests in the working guest list, may be evaluatedto determine whether one or more than one other guest is participatingin the event. If only one other guest is participating, the custom eventguest list string can indicate the first name or an avatar, handle, orother identifier associated with the other guest, as indicated at block1115. An example custom event subject for such a situation may be thecore event name (e.g., “Lunch”), the connector word (e.g., “with”), andthe custom event guest list string indicating the other guest besidesthe current user. For a Lunch with Dave and Adam, Dave's custom eventsubject will be “Lunch with Adam” and Adam's custom event subject willbe “Lunch with Dave”.

When more than one other user is in the working guest list, process 1100will continue. In some embodiments, process 1100 will perform a sort orprioritization of the working guest list at block 1120. Any suitableprioritization scheme may be utilized. In some embodiments, guestsregistered with a particular calendaring application or system may begiven higher priority than other non-registered guests. In someembodiments, guests appearing in a user's address book may be givenhigher priority than other guests. In some embodiments, guests that theuser is participating in other calendar events with may be given higherpriority than other guests. In some embodiments, prioritization may bedetermined alphabetically or according to some other generic sortingalgorithm. In some embodiments, prioritization may be determined basedon location data. For example, guests having location history closer inproximity to location history of the user may be given priority overother guests. In some embodiments, a guest corresponding to a host forthe event or a creator or organizer of the calendar entry may be given ahigher priority than other guests. In some cases, the guest list is notsorted, so that block 1120 is optional.

At block 1125, the names of the guests on the working guest list aredetermined, and optionally added to or included on a list of names. Forexample, first names may be used or other display names, such as anavatar, handle, or other name may be used if so indicated and/oraccording to user preference.

At block 1130, names that are null or that are empty may be removed fromthe list of names and at block 1135, these null or empty names may becounted. As an example, null or empty names may be associated withguests not registered with a particular calendaring application orsystem. In some cases, an email address, phone number, or otherinformation used for inviting guests with null or empty names may beoptionally used in place of a null or empty name. At block 1140, thenumber of guests with valid names may also be determined. Valid namesare those that are not null or empty. In the case of substitution withemail address, phone number, or other information, such names may beconsidered valid.

The number of valid and invalid names may be used for building anappropriate custom suffix for the custom guest list string, such as atblock 1150. A custom suffix may indicate a generic indicator of thenumber of names or guests in excess of a display number or maximumnumber of names (e.g., an excess guest count) to display as furtherdescribed below with reference to FIG. 12. This number of guests inexcess of the display number may be determined at block 1145, such as bycomputing the difference between the number of guests in the workingguest list, which may be the number of invalid names plus the number ofvalid names, and the maximum number of names to display. In otherembodiments, the excess guest count may be determined by evaluating acutoff based on the number of characters or typographical space taken upby the names in the list. For example, if the guests include mostlyshort names such as “Ed” or “Jo”, then the cutoff for excess guests mayinclude more guests than if the guest list included longer names.

Turning next to FIG. 12, a flowchart illustrating an example of aprocess 1200 for generating a custom suffix for use in a dynamic eventsubject is depicted. The custom suffix may be used to indicate how manyguests are participating in an event in excess of a number of namesincluded in a custom event guest list string. Block 1205 showsinformation used for generating a custom suffix, which may be optionallyreceived as input or be included with or derived from a calendar dataentry. Here, the information used for generating a custom suffix may bea number of valid names, an excess guest count, and a language. Anexample custom suffix may be “one other person” or “two other people” or“three others” or the like.

At block 1210, the number of valid names may be evaluated to determinewhether there are any valid names. If the number of valid names is zero,meaning no names will be included as part of a custom guest list string,no suffix first part or prefix is needed and so a null or empty customsuffix first part or prefix may be used, as shown at block 1215. Thismay be useful for a custom event subject of “Lunch with 3 others”, forexample, where ‘3 others’ represents the suffix second part, asdescribed below.

When there are some valid names to represent with the custom suffix,process 1200 may instead proceed to block 1220, where a suffix firstpart or prefix is identified for use in the custom suffix. Here thesuffix first part is identified as ‘and’, which may be translated, ifdesired or needed. Such a suffix first part may be useful in a customevent subject of “Lunch with Dave and 3 others”, where ‘and’ is thesuffix first part and ‘3 others’ represents the suffix second part, asdescribed below.

After determining a suffix first part or prefix, process 1200 mayproceed to block 1225, where an excess guest count is evaluated, such asto determine whether the excess guest count includes zero, one, or morethan one guests. When the excess guest count is zero, the custom suffixis not needed, as indicated by a custom suffix of an empty string ornull at block 1230, since this means that all guests names are displayedas part of the custom guest list string. When the excess guest count isone, the custom suffix is not needed, as indicated by a custom suffix ofan empty string or null at block 1230, since it may be preferable tospecify the name explicitly, rather than saying “1 other person”. Whenthe excess guest count is greater than one, the custom suffix maycorrespond to “X other people” or “X others” or “X other guests” or avariation of this, optionally translated to a desired language, andoptionally translated to a desired language, as indicated at block 1240.

Turning back to FIG. 11, once the custom suffix is determined at block1150, process 1100 may proceed to block 1155, where the number of validnames is evaluated to determine whether the number of valid names iszero, one, or greater than 1. For zero valid names, the custom guestlist string may be the custom suffix, as indicated at block 1160.Example custom event subjects associated with this scenario may be“Lunch with 3 others”.

For one valid name to display, the custom guest list string may be theone valid name to display and the custom suffix, as indicated at block1165. Example custom event subjects associated with this scenario may be“Lunch with Dave and John” or “Lunch with Dave and 3 others”.

For more than one valid name to display, process 1100 may optionallycheck for duplicate names at block 1170. Such a situation may be usefulfor limiting confusing custom event subjects, such as where two usershave the same name (e.g., Michael and Michael). Duplicates may beeliminated using any of a variety of techniques, such as by usingavatars, handles, email addresses, surnames, nicknames, or initials. Asan example, the duplicate guest names Michael and Michael may bemodified to Michael H. and Michael R. or to Mike and Michael.

At block 1175, the number of valid names is further evaluated todetermine whether there are two valid names to display or more than twovalid names to display. If two valid names are displayed, these namesmay be separated by the word “and” or a translation thereof, asindicated at block 1180. Example custom event subjects associated withthis scenario may be “Lunch with Dave and Adam” or “Lunch with Dave andAdam and 3 others”.

If more than two valid names are displayed, these names may be separatedserially by commas and the word “and” or a translation thereof, asindicated at block 1185. Example custom event subjects associated withthis scenario may be “Lunch with Dave, Michael, and Adam” or “Lunch withDave, Michael, and Adam and 3 others”.

It will be appreciated that the processes 1000, 1100, and 1200 may beperformed multiple times, such as at least once for each guestparticipating in the event, to generate different custom event subjectsfor each guest.

Aspects described herein may be further understood by reference to thefollowing non-limiting examples.

Example 1: Custom Event Subjects for Event Involving Two Users

This example describes an example of custom events used for an eventinvolving two users with no translation needed. In this example, Amandacreates an event and invites Kacey to participate, such as by usingKacey's email address, phone number, handle, avatar, user ID, or thelike. Amanda indicates a core event name of “Coffee” and indicates adate, time, duration, and location for the event. In this example,Amanda is the host so she may be automatically indicated as acceptingthe event invitation. In some cases, Amanda may need to separatelyindicate she is accepting the event invitation, despite being identifiedas the host. In this example, Kacey also indicates she accepts the eventinvitation.

FIG. 13A, FIG. 13B, FIG. 13C, and FIG. 13D provide schematicillustrations of calendar data entries with custom event subjects forthe event involving Amanda and Kacey. FIG. 13A and FIG. 13C showabbreviated views of the calendar data entries. FIG. 13B and FIG. 13Dshow details associated with the calendar data entries.

The custom event subject used for each of Amanda's and Kacey's calendardata entry can each be determined according to processes 1000 and 1100.

For Kacey, block 1010 proceeds to block 1020 since Kacey is not adeclined guest. At block 1020, Amanda's name is not removed from theworking guest list since she is not a declined guest. At block 1025,Kacey is removed from the working guest list since she is the currentuser. At block 1030, the number of guests in the working list isdetermined to be 1, so block 1035 proceeds to block 1045. A custom eventguest list string is generated by block 1045 according to process 1100.The custom event guest list string proceeds from block 1110 to block1115, since the number of guests besides Kacey is 1, so the custom eventguest list string is “Amanda”. Process 1000 then proceeds to block 1050and 1060 since the custom event guest list string is not empty or null,resulting in a custom event subject of “Coffee with Amanda”, as shown inFIG. 13A.

For Amanda, block 1010 proceeds to block 1020 since Amanda is not adeclined guest. At block 1020, Kacey's name is not removed from theworking guest list since she is not a declined guest. At block 1025,Amanda is removed from the working guest list since she is the currentuser. At block 1030, the number of guests in the working list isdetermined to be 1, so block 1035 proceeds to block 1045. A custom eventguest list string is generated by block 1045 according to process 1100.The custom event guest list string proceeds from block 1110 to block1115, since the number of guests besides Amanda is 1, so the customevent guest list string is “Kacey”. Process 1000 then proceeds to block1050 and 1060 since the custom event guest list string is not empty ornull, resulting in a custom event subject of “Coffee with Kacey”, asshown in FIG. 13C.

The detailed event information can also include the custom eventsubject, and can indicate the other participants, such as depicted inFIGS. 13B and 13C. The current user can be indicated as “You”, the hostor organizer can also be indicated, and the user's indication ofaccepting or going, tentative or maybe, or declining can be indicated.

Example 2: Custom Event Subjects for Event Involving Three Users

This example describes an example of custom events used for an eventinvolving three users with no translation needed. In this example, Haleycreates an event and invites Richard and Kacey to participate, such asby using Kacey's and Richard's email addresses, phone numbers, handles,avatars, user IDs, or the like. Amanda indicates a core event name of“Meeting” and indicates a date, time, duration, and location for theevent. In this example, Haley is the host so she may be automaticallyindicated as accepting the event invitation. In some cases, Haley mayneed to separately indicate she is accepting the event invitation,despite being identified as the host. In this example, Kacey and Richardwill also indicate they accept the event invitation. FIG. 14A, FIG. 14B,and FIG. 14D provide schematic illustrations of calendar data entrieswith custom event subjects for the event involving Haley, Richard andKacey.

The custom event subject used for each of Haley's, Richard's and Kacey'scalendar data entry can each be determined according to processes 1000,1100, and 1200.

For Kacey, block 1010 proceeds to block 1020 since Kacey is not adeclined guest. At block 1020, Haley's and Richard's names are notremoved from the working guest list since they are not declined guests.At block 1025, Kacey is removed from the working guest list since she isthe current user. At block 1030, the number of guests in the workinglist is determined to be 2, so block 1035 proceeds to block 1045. Acustom event guest list string is generated by block 1045 according toprocess 1100. The custom event guest list string proceeds from block1120 to block 1115, since the number of guests besides Kacey is 2. Theworking guest list includes Haley and Richard. The working guest list issorted at block 1120, such as by placing Haley first since she is thehost or organizer. The names of Haley and Richard may be retrieved atblock 1125, and no names are null or empty so block 1130 is skipped andblock 1135 gives zero number of invalid names. Block 1140 gives 2 validnames and assuming that the number of names to display is 2 or more, theexcess guest count determined at block 1145 is zero. At block 1150, thecustom suffix is determined according to process 1200. At block 1200 thenumber of valid names in excess of those displayed is 0, so the prefixis set to empty at block 1215. The excess guest count is 0 so block 1225forwards to 1230 where the custom suffix is set to empty. From block1150, process 1100 proceeds to block 1155, where the number of validnames is greater than 1. No duplicates are identified at block 1170. Thenumber of valid names is 2 so block 1175 forwards to block 1180 and thecustom event guest list string is “Haley and Richard”. Process 1000 thenproceeds to block 1050 and 1060 since the custom event guest list stringis not empty or null, resulting in a custom event subject of “Meetingwith Haley and Richard”, as shown in FIG. 14A.

For Haley, block 1010 proceeds to block 1020 since Kacey is not adeclined guest. At block 1020, Kacey's and Richard's names are notremoved from the working guest list since they are not declined guests.At block 1025, Haley is removed from the working guest list since she isthe current user. At block 1030, the number of guests in the workinglist is determined to be 2, so block 1035 proceeds to block 1045. Acustom event guest list string is generated by block 1045 according toprocess 1100. The custom event guest list string proceeds from block1120 to block 1115, since the number of guests besides Haley is 2. Theworking guest list includes Richard and Kacey. The working guest list issorted at block 1120, such as by placing Kacey first, such as if sortingalphabetically. The names of Kacey and Richard may be retrieved at block1125, and no names are null or empty so block 1130 is skipped and block1135 gives zero number of invalid names. Block 1140 gives 2 valid namesand assuming that the number of names to display is 2 or more, theexcess guest count determined at block 1145 is zero. At block 1150, thecustom suffix is determined according to process 1200. At block 1200 thenumber of valid names in excess of those displayed is 0, so the prefixis set to empty at block 1215. The excess guest count is 0 so block 1225forwards to 1230 where the custom suffix is set to empty. From block1150, process 1100 proceeds to block 1155, where the number of validnames is greater than 1. No duplicates are identified at block 1170. Thenumber of valid names is 2 so block 1175 forwards to block 1080 and thecustom event guest list string is “Kacey and Richard”. Process 1000 thenproceeds to block 1050 and 1060 since the custom event guest list stringis not empty or null, resulting in a custom event subject of “Meetingwith Kacey and Richard”, as shown in FIG. 14B.

For Richard, block 1010 proceeds to block 1020 since Richard is not adeclined guest. At block 1020, Haley's and Kacey's names are not removedfrom the working guest list since they are not declined guests. At block1025, Richard is removed from the working guest list since he is thecurrent user. At block 1030, the number of guests in the working list isdetermined to be 2, so block 1035 proceeds to block 1045. A custom eventguest list string is generated by block 1045 according to process 1100.The custom event guest list string proceeds from block 1120 to block1115, since the number of guests besides Richard is 2. The working guestlist includes Kacey and Haley. The working guest list is sorted at block1120, such as by placing Haley first since she is the host or organizer.The names of Haley and Kacey may be retrieved at block 1125, and nonames are null or empty so block 1130 is skipped and block 1135 giveszero number of invalid names. Block 1140 gives 2 valid names andassuming that the number of names to display is 2 or more, the excessguest count determined at block 1145 is zero. At block 1150, the customsuffix is determined according to process 1200. At block 1200 the numberof valid names in excess of those displayed is 0, so the prefix is setto empty at block 1215. The excess guest count is 0 so block 1225forwards to 1230 where the custom suffix is set to empty. From block1150, process 1100 proceeds to block 1155, where the number of validnames is greater than 1. No duplicates are identified at block 1170. Thenumber of valid names is 2 so block 1175 forwards to block 1180 and thecustom event guest list string is “Haley and Kacey”. Process 1000 thenproceeds to block 1050 and 1060 since the custom event guest list stringis not empty or null, resulting in a custom event subject of “Meetingwith Haley and Kacey”, as shown in FIG. 14A.

Example 3: Custom Event Subjects for Event Involving Six Users

This example describes an example of custom events used for an eventinvolving six users with no translation needed. In this example, Haleycreates an event and invites Richard, Amanda, Artemi, Till, and Kacey toparticipate, such as by using email addresses, phone numbers, handles,avatars, user IDs, or the like. Haley indicates a core event name of“Drinks” and indicates a date, time, duration, and location for theevent. In this scenario, Haley is the host so she may be automaticallyindicated as accepting the event invitation. In some cases, Haley mayneed to separately indicate she is accepting the event invitation,despite being identified as the host. In this example, Till declines toaccept the event invitation. Kacey and Amanda indicate they accept theevent invitation. Artemi provides a tentative or maybe response, andRichard does not respond. FIG. 15A, FIG. 15B, and FIG. 15D provideschematic illustrations of calendar data entries with custom eventsubjects for Kacey, Haley, and Amanda.

The custom event subject used for each guest's calendar data entry caneach be determined according to processes 1000, 1100, and 1200.

For Kacey, block 1010 proceeds to block 1020 since Kacey is not adeclined guest. At block 1020, Till's name is removed from the workingguest list since they declined. At block 1025, Kacey is removed from theworking guest list since she is the current user. At block 1030, thenumber of guests in the working list is determined to be 4, so block1035 proceeds to block 1045. A custom event guest list string isgenerated by block 1045 according to process 1100. The custom eventguest list string proceeds from block 1120 to block 1115, since thenumber of guests besides Kacey is 4. The working guest list includesAmanda, Haley, Artemi, and Richard. The working guest list is sorted atblock 1120, such as by placing Haley first since she is the host ororganizer and Amanda second since she is first alphabetically. The namesof Amanda, Haley, Artemi, and Richard may be retrieved at block 1125,and no names are null or empty so block 1130 is skipped and block 1135gives zero number of invalid names. Block 1140 gives 4 valid names andassuming that the number of names to display is 2, the excess guestcount determined at block 1145 is 2. At block 1150, the custom suffix isdetermined according to process 1200. At block 1200 the number of validnames in excess of those displayed is 2, so the prefix is set to ‘and’at block 1215. The excess guest count is 2 so block 1225 forwards to1240 where the custom suffix is set to “2 others”. From block 1150,process 1100 proceeds to block 1155, where the number of valid names isgreater than 1. No duplicates are identified at block 1170. The numberof valid names is 4 so block 1175 forwards to block 1180 and the customevent guest list string is “Haley, Amanda, and 2 others”. Process 1000then proceeds to block 1050 and 1060 since the custom event guest liststring is not empty or null, resulting in a custom event subject of“Drinks with Haley, Amanda, and 2 others”, as shown in FIG. 15A.

For Haley, block 1010 proceeds to block 1020 since Haley is not adeclined guest. At block 1020, Till's name is removed from the workingguest list since they declined. At block 1025, Haley is removed from theworking guest list since she is the current user. At block 1030, thenumber of guests in the working list is determined to be 4, so block1035 proceeds to block 1045. A custom event guest list string isgenerated by block 1045 according to process 1100. The custom eventguest list string proceeds from block 1120 to block 1115, since thenumber of guests besides Haley is 4. The working guest list includesAmanda, Kacey, Artemi, and Richard. The working guest list is sorted atblock 1120, such as by placing Kacey first since she may be in Haley'saddress book, and Amanda second since she is first alphabetically. Thenames of Amanda, Kacey, Artemi, and Richard may be retrieved at block1125, and no names are null or empty so block 1130 is skipped and block1135 gives zero number of invalid names. Block 1140 gives 4 valid namesand assuming that the number of names to display is 2, the excess guestcount determined at block 1145 is 2. At block 1150, the custom suffix isdetermined according to process 1200. At block 1200 the number of validnames in excess of those displayed is 2, so the prefix is set to ‘and’at block 1215. The excess guest count is 2 so block 1225 forwards to1240 where the custom suffix is set to “2 others”. From block 1150,process 1100 proceeds to block 1155, where the number of valid names isgreater than 1. No duplicates are identified at block 1170. The numberof valid names is 4 so block 1175 forwards to block 1180 and the customevent guest list string is “Kacey, Amanda, and 2 others”. Process 1000then proceeds to block 1050 and 1060 since the custom event guest liststring is not empty or null, resulting in a custom event subject of“Drinks with Kacey, Amanda, and 2 others”, as shown in FIG. 15B.

For Amanda, block 1010 proceeds to block 1020 since Amanda is not adeclined guest. At block 1020, Till's name is removed from the workingguest list since they declined. At block 1025, Amanda is removed fromthe working guest list since she is the current user. At block 1030, thenumber of guests in the working list is determined to be 4, so block1035 proceeds to block 1045. A custom event guest list string isgenerated by block 1045 according to process 1100. The custom eventguest list string proceeds from block 1120 to block 1115, since thenumber of guests besides Amanda is 4. The working guest list includesHaley, Kacey, Artemi, and Richard. The working guest list is sorted atblock 1120, such as by placing Haley first since she is the host ororganizer and Kacey second since she may be in Amanda's address book.The names of Haley, Kacey, Artemi, and Richard may be retrieved at block1125, and no names are null or empty so block 1130 is skipped and block1135 gives zero number of invalid names. Block 1140 gives 4 valid namesand assuming that the number of names to display is 2, the excess guestcount determined at block 1145 is 2. At block 1150, the custom suffix isdetermined according to process 1200. At block 1200 the number of validnames in excess of those displayed is 2, so the prefix is set to ‘and’at block 1215. The excess guest count is 2 so block 1225 forwards to1240 where the custom suffix is set to “2 others”. From block 1150,process 1100 proceeds to block 1155, where the number of valid names isgreater than 1. No duplicates are identified at block 1170. The numberof valid names is 4 so block 1175 forwards to block 1180 and the customevent guest list string is “Haley, Kacey, and 2 others”. Process 1000then proceeds to block 1050 and 1060 since the custom event guest liststring is not empty or null, resulting in a custom event subject of“Drinks with Haley, Kacey, and 2 others”, as shown in FIG. 15B.

The determination of the custom event subjects may proceed similarly forRichard, and Artemi. For Till, the process of generating the customevent string may end at block 1015 since Till is a declined user.

Specific details were given in the preceding description to provide athorough understanding of various examples of systems and components foran event monitoring system. It will be understood by one of ordinaryskill in the art, however, that the examples described above may bepracticed without these specific details. For example, circuits,systems, networks, processes, and other components may be shown ascomponents in block diagram form in order not to obscure the examples inunnecessary detail. In other instances, well-known circuits, processes,algorithms, structures, and techniques may be shown without unnecessarydetail in order to avoid obscuring the examples.

It is also noted that individual implementations may be described as aprocess which is depicted as a flowchart, a flow diagram, a data flowdiagram, a structure diagram, or a block diagram. Although a flowchartmay describe the operations as a sequential process, many of theoperations can be performed in parallel or concurrently. In addition,the order of the operations may be re-arranged. A process is terminatedwhen its operations are completed, but could have additional steps notincluded in a figure. A process may correspond to a method, a function,a procedure, a subroutine, a subprogram, etc. When a process correspondsto a function, its termination can correspond to a return of thefunction to the calling function or the main function.

The term “computer-readable medium” includes, but is not limited to,portable or non-portable storage devices, optical storage devices, andvarious other mediums capable of storing, containing, or carryinginstruction(s) and/or data. A computer-readable medium may include anon-transitory medium in which data can be stored and that does notinclude carrier waves and/or transitory electronic signals propagatingwirelessly or over wired connections. Examples of a non-transitorymedium may include, but are not limited to, a magnetic disk or tape,optical storage media such as compact disk (CD) or digital versatiledisk (DVD), flash memory, memory or memory devices. A computer-readablemedium may have stored thereon code and/or machine-executableinstructions that may represent a procedure, a function, a subprogram, aprogram, a routine, a subroutine, a module, a software package, a class,or any combination of instructions, data structures, or programstatements. A code segment may be coupled to another code segment or ahardware circuit by passing and/or receiving information, data,arguments, parameters, or memory contents. Information, arguments,parameters, data, etc. may be passed, forwarded, or transmitted via anysuitable means including memory sharing, message passing, token passing,network transmission, or the like.

The various examples discussed above may further be implemented byhardware, software, firmware, middleware, microcode, hardwaredescription languages, or any combination thereof. When implemented insoftware, firmware, middleware or microcode, the program code or codesegments to perform the necessary tasks (e.g., a computer-programproduct) may be stored in a computer-readable or machine-readablestorage medium (e.g., a medium for storing program code or codesegments). One or more processors, implemented in an integrated circuit,may perform the necessary tasks.

Where components are described as being “configured to” or “operable to”perform certain operations, such configuration or operation can beaccomplished, for example, by designing electronic circuits or otherhardware to perform the operation, by programming programmableelectronic circuits (e.g., microprocessors, or other suitable electroniccircuits) to perform the operation, or any combination thereof.

The various illustrative logical blocks, modules, circuits, andalgorithm steps described in connection with the examples disclosedherein may be implemented as electronic hardware, computer software,firmware, or combinations thereof. To clearly illustrate thisinterchangeability of hardware and software, various illustrativecomponents, blocks, modules, circuits, and steps have been describedabove generally in terms of their functionality. Whether suchfunctionality is implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem. Skilled artisans may implement the described functionality invarying ways for each particular application, but such implementationdecisions should not be interpreted as causing a departure from thescope of the examples presented herein.

The techniques described herein may also be implemented in electronichardware, computer software, firmware, or any combination thereof. Suchtechniques may be implemented in any of a variety of devices such asgeneral purposes computers, wireless communication device handsets, orintegrated circuit devices having multiple uses including application inwireless communication device handsets and other devices. Any featuresdescribed as modules or components may be implemented together in anintegrated circuit logic device or separately as discrete butinteroperable logic devices. If implemented in software, the techniquesmay be realized at least in part by a computer-readable data storagemedium comprising program code including instructions that, whenexecuted, performs one or more of the methods described above. Thecomputer-readable data storage medium may form part of a computerprogram product, which may include packaging materials. Thecomputer-readable medium may comprise memory or data storage media, suchas random access memory (RAM) such as synchronous dynamic random accessmemory (SDRAM), read-only memory (ROM), non-volatile random accessmemory (NVRAM), electrically erasable programmable read-only memory(EEPROM), FLASH memory, magnetic or optical data storage media, and thelike. The techniques additionally, or alternatively, may be realized atleast in part by a computer-readable communication medium that carriesor communicates program code in the form of instructions or datastructures and that can be accessed, read, and/or executed by acomputer, such as propagated signals or waves.

The program code may be executed by a processor (which may include oneor more processors or processor cores), such as one or more digitalsignal processors (DSPs), general purpose microprocessors, anapplication specific integrated circuits (ASICs), field programmablelogic arrays (FPGAs), or other equivalent integrated or discrete logiccircuitry. Such a processor may be configured to perform any of thetechniques described in this disclosure. A general purpose processor maybe a microprocessor; but in the alternative, the processor may be anyconventional processor, controller, microcontroller, or state machine. Aprocessor may also be implemented as a combination of computing devices,e.g., a combination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration. Accordingly, the term“processor,” as used herein may refer to any of the foregoing structure,any combination of the foregoing structure, or any other structure orapparatus suitable for implementation of the techniques describedherein. In addition, in some aspects, the functionality described hereinmay be provided within dedicated software modules or hardware modules.

What is claimed is:
 1. A method for coordinating event entries betweencomputers comprising: receiving, at a server computer, inputcorresponding to a calendar data entry originating from an originatingcomputer the calendar data entry including an event start time, one ormore user identifiers, and a base event subject; generating, using thecalendar data entry, one or more custom calendar data entriesrespectively associated with the one or more user identifiers, wherein acustom calendar data entry includes a respective custom event subjectfor a respective user identifier and the event start time, therespective custom event subject derived from the base event subject andthe one or more user identifiers; transmitting the one or more customcalendar data entries for adding an event to calendar files associatedwith the one or more user identifiers to one or more computers;generating a particular custom calendar data entry respectivelyassociated with a particular user identifier from the one or more useridentifiers at each of the one or more computers; determining a numberof quests for the event using the one or more user identifiers; whereina guest may be a user associated with the particular user identifier;determining a particular custom event subject using the number of questsfor the event, the base event subject, and the one or more useridentifiers; identifying a connector word for the particular customevent subject; determining a custom event guest list string for aparticular custom calendar entry subject using the number of guests forthe event and the one or more user identifiers; generating theparticular custom event subject using the base event subject, theconnector word, and the custom event quest list string; determining atotal number of guests for the custom event guest list string using thenumber of guests, the number of guests not counting the particular useridentifier; generating a quest list comprising names associated with theone or more user identifiers, the quest list not including a nameassociated with the particular user identifier; determining a maximumnumber of names to be displayed in the custom event guest list string;determining an excess quest count, the excess quest count correspondingto a difference between the number of quests and the maximum number ofnames; automatically tracking one or more of proximity locationhistories of one or more guest portable devices corresponding to thequest list during a monitoring period; automatically updating the one ormore proximity location histories of the one or more quest portabledevices; automatically updating the custom event quest list string basedon the one or more proximity location histories of the one or more questportable devices; automatically ranking the number of guests based on asubset of number of guests having a proximity location history closer toa location associated with the particular user identifier; automaticallyupdating the custom event quest list string based on the ranking; andautomatically disabling gathering of the proximity location history ofthe one or more quest portable devices after the monitoring period. 2.The method of claim 1, wherein the custom calendar data entry furtherincludes one or more of an event end time, an event duration, alocation, a geolocation, an address, one or more user identifiers, anevent recurrence schedule, or any combination of these.
 3. The method ofclaim 1, further comprising: determining an event status indicating thata first user associated with a first user identifier of the one or moreuser identifiers has accepted a request to be included in the event; andgenerating one or more updated custom calendar data entries respectivelyassociated with the one or more user identifiers, the one or moreupdated custom calendar data entries including the first useridentifier.
 4. The method of claim 3, wherein: the one or more updatedcustom calendar data entries further include an indication of acceptanceby the first user; or the one or more updated custom calendar dataentries include an updated custom event subject including the first useridentifier or a name associated with the first user identifier.
 5. Themethod of claim 1, further comprising: determining an event typeindicating that a calendar event is host centric event; whereingenerating the one or more custom calendar data entries respectivelyassociated with the one or more user identifiers includes: generating ahost custom event subject for a host custom calendar data entry; andgenerating a guest custom event subject for one or more guest customcalendar data entries.
 6. The method of claim 1, further comprising:determining an event status indicating that a first user associated witha first user identifier of the one or more user identifiers has rejecteda request to be included in the event; removing the first useridentifier from a list of the one or more user identifiers; andgenerating one or more updated custom calendar data entries respectivelyassociated with the list of the one or more user identifiers.
 7. Themethod of claim 6, wherein: the one or more updated custom calendar dataentries further include an indication of rejection by the first user; orthe one or more updated custom calendar data entries include an updatedcustom event subject lacking the first user identifier or a nameassociated with the first user identifier; or the one or more updatedcustom calendar data entries lack the first user identifier.
 8. Themethod of claim 1, wherein determining the custom event guest liststring comprises: generating a suffix for the custom event guest liststring using the excess guest count; and generating the custom eventguest list string using the guest list, and the suffix.
 9. The method ofclaim 8, wherein determining the custom event guest list string furthercomprises: sorting or prioritizing the names in the guest list.
 10. Themethod of claim 8, wherein determining the custom event guest liststring further comprises: modifying the guest list to eliminateduplicate names or invalid names.
 11. The method of claim 8, whereingenerating the suffix comprises: identifying a suffix first part usingthe number of guests; and identifying a suffix second part using theexcess guest count.
 12. A system for coordinating event entriescomprising: one or more processors; and a non-transitorycomputer-readable medium including instructions that, when executed bythe one or more processors, cause the one or more processors to performoperations including: receiving input corresponding to a calendar dataentry originating from an originating computer, the calendar data entryincluding an event start time, one or more user identifiers, and a baseevent subject; generating, using the calendar data entry, one or morecustom calendar data entries respectively associated with the one ormore user identifiers, wherein a custom calendar data entry includes arespective custom event subject for a respective user identifier and theevent start time, the respective custom event subject derived from thebase event subject and the one or more user identifiers; transmittingthe one or more custom calendar data entries for adding an event tocalendar files associated with the one or more user identifiers to oneor more computers; generating a particular custom calendar data entryrespectively associated with a particular user identifier from the oneor more user identifiers at each of the one or more computers;determining a number of quests for the event using the one or more useridentifiers; wherein a quest may be a user associated with theparticular user identifier; determining a particular custom eventsubject using the number of quests for the event, the base eventsubject, and the one or more user identifiers; identifying a connectorword for the particular custom event subject; determining a custom eventguest list string for a particular custom calendar entry subject usingthe number of guests for the event and the one or more user identifiers;generating the particular custom event subject using the base eventsubject, the connector word, and the custom event quest list string;determining a total number of guests for the custom event guest liststring using the number of guests, the number of guests not counting theparticular user identifier; generating a quest list comprising namesassociated with the one or more user identifiers, the quest list notincluding a name associated with the particular user identifier;determining a maximum number of names to be displayed in the customevent quest list string; determining an excess quest count, the excessquest count corresponding to a difference between the number of guestsand the maximum number of names; automatically tracking one or more ofproximity location histories of one or more guest portable devicescorresponding to the quest list during a monitoring period;automatically updating the one or more proximity location histories ofthe one or more quest portable devices; automatically updating thecustom event quest list string based on the one or more proximitylocation histories of the one or more quest portable devices;automatically ranking the number of guests based on a subset of numberof quests having a proximity location history closer to a locationassociated with the particular user identifier; automatically updatingthe custom event quest list string based on the ranking; andautomatically disabling gathering of the proximity location history ofthe one or more quest portable devices after the monitoring period. 13.The system of claim 12, wherein determining the custom event guest liststring comprises: generating a suffix for the custom event guest liststring using the excess guest count; and generating the custom eventguest list string using the guest list, and the suffix.
 14. Acomputer-program product for coordinating event entries betweencomputers tangibly embodied in a non-transitory machine-readable storagemedium including instructions that, when executed by one or moreprocessors of a computing device, cause the one or more processors toperform operations including: receiving input corresponding to acalendar data entry originating from an originating computer, thecalendar data entry including an event start time, one or more useridentifiers, and a base event subject; generating, using the calendardata entry, one or more custom calendar data entries respectivelyassociated with the one or more user identifiers, wherein a customcalendar data entry includes a respective custom event subject for arespective user identifier and the event start time, the respectivecustom event subject derived from the base event subject and the one ormore user identifiers; transmitting the one or more custom calendar dataentries for adding an event to calendar files associated with the one ormore user identifiers to one or more computers; generating a particularcustom calendar data entry respectively associated with a particularuser identifier from the one or more user identifiers at each of the oneor more computers; determining a number of quests for the event usingthe one or more user identifiers; wherein a quest may be a userassociated with the particular user identifier; determining a particularcustom event subject using the number of quests for the event, the baseevent subject, and the one or more user identifiers; identifying aconnector word for the particular custom event subject; determining acustom event guest list string for a particular custom calendar entrysubject using the number of guests for the event and the one or moreuser identifiers; generating the particular custom event subject usingthe base event subject, the connector word, and the custom event questlist string; determining a total number of guests for the custom eventguest list string using the number of guests, the number of guests notcounting the particular user identifier; generating a quest listcomprising names associated with the one or more user identifiers, thequest list not including a name associated with the particular useridentifier; determining a maximum number of names to be displayed in thecustom event quest list string; determining an excess quest count, theexcess quest count corresponding to a difference between the number ofquests and the maximum number of names; automatically tracking one ormore of proximity location histories of one or more guest portabledevices corresponding to the quest list during a monitoring period;automatically updating the one or more proximity location histories ofthe one or more quest portable devices; automatically updating thecustom event quest list string based on the one or more proximitylocation histories of the one or more quest portable devices;automatically ranking the number of quests based on a subset of numberof quests having a proximity location history closer to a locationassociated with the particular user identifier; automatically updatingthe custom event quest list string based on the ranking; andautomatically disabling gathering of the proximity location history ofthe one or more quest portable devices after the monitoring period. 15.The computer-program product of claim 12, wherein determining the customevent guest list string comprises: generating a suffix for the customevent guest list string using the excess guest count; and generating thecustom event guest list string using the guest list, and the suffix.